Skip to main content
We’re introducing the new Research endpoint (/research), an autonomous research agent that investigates the web to handle questions a single search query cannot resolve. The agent plans its retrieval, gathers evidence from multiple sources in parallel, iterates through investigation, and returns a sourced response with inline citations. Three modes, four reasoning depths, two output types. Asynchronous lifecycle.

How to use

  1. Send a POST /research request with a natural-language question and the parameters that pin the investigation. The endpoint immediately returns a task identifier and status of "pending".
  2. Poll GET /research/{id} to retrieve a specific task, or GET /research to list all your research tasks.
  3. While running, status is "pending" or "processing". Once the task is "completed", read the result in output. If "failed", inspect error.
Example Request
curl

Modes

If mode is not provided, the agent automatically classifies the question and selects one of the three modes for the request.

Reasoning depth

reasoningDepth controls thoroughness. Higher depths have more compute budget: they consult more sources, perform more iterations and cross-checking, produce longer outputs, and take longer to run. Omitting the parameter defaults to "L".

Output types

Billing

The Research endpoint is billed per call at a flat rate per reasoningDepth, regardless of mode. See pricing. Read the full reference: POST /research · GET /research · GET /research/:id. For operational guidance, see research best practices.