[deleted]
Response Healing: Reduce JSON defects by 80%+
21–30 of 52 posts
Re: Response Healing: Reduce JSON defects by 80%+
#22Dear Openrouter blog authors, could you please stop writing your blogposts with LLMs? The content of your posts is really insightful and interesting, but it's feel like junk quality because of the way LLMs write blogposts. What was your prompt?
A lot of it was finger written -- curious which part sounded like LLM to you?
> > Here's something most developers overlook: if an LLM has a 2% JSON defect rate, and Response Healing drops that to 1%, you haven't just made a 1% improvement. You've cut your defects, bugs, and support tickets in half.
This sounds AI written.
Re: Response Healing: Reduce JSON defects by 80%+
#23Very confused. When you enable structured output the response should adhere to the JSON schema EXACTLY, not best effort, by constraining the output via guided decoding. This is even documented in OpenRouter's structured output doc
> The model will respond with a JSON object that strictly follows your schema
Gemini is listed as a model supporting structured output, and yet its fail rate is 0.39% (Gemini 2.0 Flash)!! I get that structured output has a high performance cost but advertising it as supported when in reality it's not is a massive red flag.
Worst yet response healing only fixes JSON syntax error, not schema adherence. This is only mentioned at the end of the article which people are clearly not going to read.
WTF
Re: Response Healing: Reduce JSON defects by 80%+
#24Earlier quoted context omitted.
A lot of it was finger written -- curious which part sounded like LLM to you?
Meaning parts were LLM written? With no disclosure?
"With no disclosure?"
Why do you have an expectation that a company will disclose to you when they use AI for their copywriting? Do you want them to disclose the software they used to draft and publish? If a manager reviewed the blog post before it went live?
Re: Response Healing: Reduce JSON defects by 80%+
#25Earlier quoted context omitted.
Meaning parts were LLM written? With no disclosure?
"With no disclosure?" Why do you have an expectation that a company will disclose to you when they use AI for their copywriting? Do you want them to disclose the software they used to draft and publish? If a manager reviewed the blog post before it went live?
Why not just publish the prompt? I can then take an LLM of my taste to reformat it the way I want.
Basically, I'm asking for open source blogging!
Re: Response Healing: Reduce JSON defects by 80%+
#26>What about XML? The plugin can heal XML output as well - contact us if you’d like access.
Isn't this exactly how we got weird html parsing logic in the first place, with "autohealing" logic for mismatched closing tags or quotes?
Re: Response Healing: Reduce JSON defects by 80%+
#27> Here's something most developers overlook: if an LLM has a 2% JSON defect rate, and Response Healing drops that to 1%, you haven't just made a 1% improvement. You've cut your defects, bugs, and support tickets in half. If part of my system can't even manage to output JSON reliably, it needs way more "healing" than syntax munging. This comes across as naive.
"it's not just X, it's Y"
Don't you worry about Planet Express, let me worry about blank.
Re: Response Healing: Reduce JSON defects by 80%+
#28Is this a joke? Am I going crazy?
I don't like this future we're going towards where we have to trick our software (which we can no longer understand the workings of) into doing what we tell it to by asking it nicely, or by putting another black box on the end to "fix" the output. This is the opposite of engineering. This is negotiation with a genie trapped in silicon.
Re: Response Healing: Reduce JSON defects by 80%+
#29I did some searching for an open-source version of this and found this pretty neat library for Elixir called json_remedy
Re: Response Healing: Reduce JSON defects by 80%+
#30Is this a joke? Am I going crazy? I don't like this future we're going towards where we have to trick our software (which we can no longer understand the workings of) into doing what we tell it to by asking it nicely, or by putting another black box on the end to "fix" the output. This is the opposite of engineering. This is negotiation with a genie trapped in silicon.
it does seem as if the world has gone insane
we have brilliant machines that can more or less work perfectly
then the scam artists have convinced people that spending a trillion dollar and terawatts to get essentially a biased random number generator to produce unusable garbage is somehow an improvement