Run a bounded request through REST
Quote, submit, poll and cancel an owned search with scoped credentials.
Authenticate
Create a named, expiring API key in the authenticated developer settings. Keep it in a server-side secret store. Send Authorization: Bearer followed by the key over HTTPS. Do not put credentials or research questions in URL parameters.
Request sequence
POST /api/v1/search-quotes with question, scope and history set to session. Review maxCredits. POST /api/v1/searches with quoteId, maxCredits and an Idempotency-Key header. GET /api/v1/searches/{id} until terminal. POST /api/v1/searches/{id}/cancel stops active work; /ack removes the temporary delivered result.
Retries and errors
Repeat an uncertain start with the same key and identical body. A conflicting reuse is rejected. Respect Retry-After on rate limits; refresh an expired quote rather than changing the accepted maximum silently. A missing or expired result payload does not erase its receipt.
Contract
Download the machine-readable OpenAPI contract linked below. Search requests accept at most two explicit context turns within a combined 8,192-byte limit. Cloud writes allow 256 KiB of selected conversation JSON inside a 280 KiB HTTP body. A full Cloud export or deletion requires both history and memory permissions because it covers both kinds of data.
Related help
- Add inspectable research to your workflow
- Resolve an integration problem
- Know the cost before you search
Content revision 2026-09-07. Preview: search indexing is disabled.