Exa's Contents API returns cached pages unless you set maxAgeHours, so agents need an explicit freshness setting
Exa has replaced the string livecrawl flag with an integer maxAgeHours, folded content extraction into Search pricing, and moved errors into per-URL statuses. If you leave the freshness field out, you can get a cached snapshot that is days old, and one open-source agent already shipped that bug.
- search
- agents
- mcp