Exa · Search

Exa Public API / Create a run

Create an asynchronous Agent run. By default, the API returns the run object immediately. Set Accept: text/event-stream to stream run lifecycle events until the run reaches a terminal status.

Private Gateway connection

Data below comes from the configured private Gateway. Provider activation remains governed by its evidence and policy gates.

unverifiedRequest shape unavailableUnverified

Published API evidence

Public metadata only. Response bodies, credentials, and internal review notes are never displayed.

No verification date is claimed. No response capture is claimed.

Request parameters

budget body · optional
Optional per-run spending limit for the metered `auto` and `max` efforts. Runs that finish early may cost less than the limit.
dataSources body · optional
Exa Connect data providers to enable for the run. Each entry enables all of that provider's tools.
effort body · optional
Cost and reasoning effort preference for the run. `auto` lets Exa choose the appropriate effort. `max` is the highest-effort public beta tier for work where completeness and thoroughness matter more than latency or cost, including large list building, deep multi-source research, and criteria that are hard to verify.
input body · optional
Records to process and records or entities to exclude from the answer.
metadata body · optional
Caller-provided metadata stored with the run.
outputSchema body · optional
previousRunId body · optional
Agent run ID. New run IDs are returned with the `agent_run_` prefix. Example: "agent_run_01j7x9v0m2n4p6q8r0s2t4v6w8"
query body · required
Natural-language question or instructions for the request.
systemPrompt body · optional
Additional instructions that guide generated output or agent behavior. Use this for source preferences, novelty constraints, duplication constraints, or other behavior guidance. Example: "Prefer official sources and avoid duplicate results."

Provider docs How to run it