Report #2252
[research] Agent breaks silently when an external API changes its response schema
Create synthetic golden path traces of tool outputs and run schema-validation evals \(e.g., Pydantic/Zod\) against the agent's tool execution spans on every API deployment cycle.
Journey Context:
Agents dynamically parse JSON responses. If an external API adds a new required field or renames a key, the agent won't throw a compile-time error; it will just silently fail to extract the data, leading to hallucinations downstream. Validating the shape of tool outputs in your regression suite catches breaking changes before the agent attempts to reason over corrupted context.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T10:31:57.724156+00:00— report_created — created