Exa is included as a search provider for products that need programmatic discovery of web resources. The cost calculation starts with the number of searches, not with a broad label such as “agent” or “research assistant.” That makes the estimate portable across product designs and exposes the assumption that drives spend.
Search is one part of a research pipeline. A typical task may call a language model, submit one or more searches, and retrieve several pages. Exa covers the search component in this catalog. Page contents, extraction, and later model processing remain separate operations unless the exact offer explicitly includes them.
The current entry represents a defined result profile. Optional content retrieval or other paid features are excluded from that offer. This boundary prevents a low base search price from being presented as the full cost of a richer operation.
Scenario mode derives monthly searches from active users, research tasks per user, and searches per task. Counts are rounded at the scenario boundary and then priced. Exact mode accepts a monthly search total directly for teams that already measure production traffic.
The live offer and plan sections above are rendered from the current snapshot. They contain the API operation, billing rule, source references, and verification date. Prices are deliberately not written into this Markdown article. The pricing dataset remains the single numerical source of truth and retains immutable historical versions.
The cheapest search request is not automatically the best result for every query. Relevance, freshness, result depth, and latency require comparable evidence. The recommendation engine only uses evidence records that share an acceptable methodology and remain inside the freshness window. If that evidence is missing, cost comparison continues while Fastest or Balanced can be unavailable.
The estimate excludes taxes, infrastructure, storage, retries, and any downstream scraping or language-model work. It also excludes request modes that are not represented by the selected offer. Read the exact endpoint description in the card before mapping an application call to one billable search.
The offer action opens the calculator with Research enabled and Exa locked as the search component. Other components stay open to comparison. Change monthly users, tasks, searches, pages, and token assumptions to reflect the intended workflow.
Treat the result as a reproducible planning estimate based on the displayed catalog version. Confirm the official source and verification date before committing to a production budget.