Exa Just Removed /research and Started Silently Ignoring Two Date Filters - Your Agent Is Probably Pulling Stale Pages Right Now

The article discusses how API providers can introduce changes that break integrations silently, leading to unexpected behavior without clear errors or warnings. This is particularly relevant for services like Exa AI, where recent deprecations and parameter changes have caused issues in production systems.

Key Points:

1. Silent Failures:

   • The API still returns a 200 status code.
   • SDKs continue to validate requests as before.
   • Fields or parameters that your application depends on are either ignored, return null, or are removed entirely without explicit warnings.

2. Examples of Silent Changes:

   • Exa AI: Deprecation of /research endpoint and crawl-date filters returning silently ignored parameters.
   • Stripe Basil: Moving current_period_end to items[].current_period_end.
   • GitHub: Returning null for pull_request.merge_commit_sha on closed PRs.
   • OpenAI: Rejecting input_text with an "Invalid value" error.

3. Detection and Mitigation:

   • Audit Codebase: Search for deprecated parameters or fields in your code.
   • Daily Monitoring Scripts: Hash the response field set and alert

Read the full article at DEV Community

---

Want to create content about this topic? Use Nemati AI tools to generate articles, social posts, and more.