Changelog

The Answer API (POST /v1/answer) returns a synthesized, citation-backed answer to a question in one call. It retrieves web results from a single search, verifies citations against the source text, and returns a Markdown answer with inline citations — no orchestrating retrieval, page reads, prompts, or model selection on your end. It is designed to be focused and fast.

GET /v1/search and POST /v1/finance_research now accept machine payments, so an agent with a funded wallet can call either one without an API key, an account, or a prepaid credit balance. Payment settles inside the same HTTP exchange that requests the data.

Two protocols are advertised on both routes, and a single unpaid request returns terms for each:

The Research API now supports a background parameter on POST /v1/research. Set background: true to queue the request as an asynchronous task and receive a task handle immediately, instead of waiting for the final answer inline. Poll GET /v1/research/{task_id} for status and results, or stream real-time progress via GET /v1/research/{task_id}/stream using Server-Sent Events.

A new frontier effort level is available for long-running, deep research tasks that require the maximum compute budget. Frontier is priced at $1,200 per 1k requests, with latency ranging from 30s to 12000s (p50: 300s).

Frontier requires background: true — synchronous requests with research_effort: "frontier" return 422. Structured output via output_schema is supported.

The authors field is no longer included in Web Search API v1 search results or Answer API source results. The field has been removed from both response schemas and all related documentation. The v0 (legacy) search API was not affected, as it did not include this field.

Review the updated response schemas in the Web Search API guide and the Answer API reference.