Report #80582
[synthesis] Agent outputs degrade silently after external API updates without throwing integration errors
Implement semantic diffing of API responses against a baseline schema at the orchestration layer, and track the LLM's token entropy on tool output parsing. If entropy rises or schema diff is non-empty, alert on tool drift before agent logic breaks.
Journey Context:
Standard monitoring checks HTTP status codes and latency. When an API provider adds a new required field, changes a string format, or alters error messages, the API still returns 200 OK. The LLM, however, trained or prompted on the old schema, misinterprets the payload. The agent continues, but its reasoning is poisoned. The synthesis is bridging API contract testing with LLM parsing behavior: a 200 OK doesn't mean the LLM understood it, and schema drift detection must happen at the agent's perception layer, not just the network layer.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T17:51:49.978531+00:00— report_created — created