Evidence-led Exa search

Use the official SDK or an available authorised Exa tool. The old Python HTTP wrappers and their compatibility flags are removed. For an application, inspect and record the installed SDK version; use its actual types, not a cached parameter catalogue. Keep API keys in secret storage/environment, not arguments or logs.

Search, inspect, then expand

1. Define the question, date interval, relevant geography, source requirements, and a request/content budget. Prefer public primary sources for technical claims.
2. Start with 5–10 results and bounded highlights. Use a category or domain filter only when it expresses an actual constraint; do not combine every available filter.
3. Inspect coverage and evidence, deduplicate syndicated/near-identical pages, and fetch fuller content for the sources supporting material claims.
4. Expand the query only for a named evidence gap. Stop when the question is answered or the budget is reached; report unresolved gaps and retrieval failures.