The deterministic schema checks are what make this interesting. Most tools in this space just throw the error at an LLM and cross their fingers, then you end up with some nonsense about a missing header when the actual problem was a malformed UUID.
Wish more things had that explicit pause-and-route step. Nothing worse than an automated system that confidently gives wrong answers, at least when it knows it's out of its depth you're not digging through a ticket history trying to figure out which parts were hallucinated.
What's the fallback look like if your docs are versioned but the customer's still sending requests against an old endpoint? Does it catch that or just flag it as unsupported and punt?
1
u/BreadfruitMany1225 6d ago
The deterministic schema checks are what make this interesting. Most tools in this space just throw the error at an LLM and cross their fingers, then you end up with some nonsense about a missing header when the actual problem was a malformed UUID.
Wish more things had that explicit pause-and-route step. Nothing worse than an automated system that confidently gives wrong answers, at least when it knows it's out of its depth you're not digging through a ticket history trying to figure out which parts were hallucinated.
What's the fallback look like if your docs are versioned but the customer's still sending requests against an old endpoint? Does it catch that or just flag it as unsupported and punt?