Skip to main content
Exa Snapshot keeps stored versions of pages Exa has crawled. Send snapshotAsOf to pin the request to a datetime. Use this to backtest agents, run reproducible evals, and compare earlier versions of docs, pricing pages, policies, and filings.
Exa Snapshot is available on pay as you go at 10 QPS, with a rolling 5-month index window. After 100 requests, talk to sales to continue.

Pin contents to a datetime

Add snapshotAsOf at the top level of a /contents request.
Exa returns the newest stored version at or before that datetime.
IDs with no eligible version are omitted from results and reported in statuses with "status": "error" and "tag": "CONTENT_NOT_CACHED".

Search at a datetime

On /search, put snapshotAsOf inside contents.
Exa discovers candidate URLs, then keeps only pages with a stored version at or before snapshotAsOf.

How snapshots work

For both endpoints:
  • Returned page content comes from that stored version.
  • Title, author, publication date, text, highlights, and summaries are generated only from that version.
  • Pages without an eligible version in the 5-month window are omitted.
On Search, the cutoff bounds content, not ranking. Exa still uses current retrieval signals to discover candidate URLs. Use the results as evidence bounded by snapshotAsOf, not as an exact reconstruction of what a search would have ranked at that time.

Limits and compatibility

Pay as you go includes 10 QPS and a rolling 5 months of index access. A snapshotAsOf older than that window is rejected. After 100 requests, talk to sales to continue.
Do not combine snapshotAsOf with options that can reach the live web or expand to other pages. Omit livecrawl, livecrawlTimeout, maxAgeHours, and subpages entirely; requests that set any of them alongside snapshotAsOf are rejected with INVALID_REQUEST.
Exa Snapshot on Search supports auto, fast, and instant. It does not support deep-lite, deep, or deep-reasoning.Exa Snapshot does not support the category parameter on Search.

Common uses

Use Exa Snapshot when the task depends on what Exa had stored by a specific datetime:
  • Backtest an agent without exposing it to later page updates.
  • Run an evaluation against a repeatable content boundary.
  • Compare earlier versions of documentation, pricing, policies, or filings.
Last modified on September 17, 2026