Docs

Web search

Search configured open-web providers through one authenticated Scry endpoint.

Request

POST /v1/scry/web accepts JSON with a non-empty q. Queries may contain at most 400 characters. limit defaults to 10 and is clamped from 1 through 20. The optional providers array accepts exa and google; omit it to call every configured provider.

curl -X POST https://api.scry.io/v1/scry/web \
  -H "Authorization: Bearer $SCRY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"q":"mechanistic interpretability survey","limit":10}'

Response

The response status is ok, partial, or unconfigured. Results include provider, provider rank, title, URL, and optional snippet and publication date. The providers object reports each provider as ok, unavailable, or unconfigured, with result count and available latency or error details.

Trust and charging

Titles and snippets are third-party text and arrive inside Scry’s untrusted-content fence. API-key calls reserve funds before provider requests and charge only providers that answer. Session calls use a shared decaying budget. The agent contract prices web search at $0.0075 per answering provider.

Related docs

HTTP API Use the Scry HTTP API for context, schema discovery, bounded read-only SQL, reranking, and web search.Pricing and limits Understand Scry credits, congestion pricing, query metering, and the limits that keep requests bounded.Errors Handle Scry HTTP error envelopes, status codes, retry guidance, and long-query failures.