Deep Scrape

Collect structured evidence about one subject across public sources. Use deep-research for detailed answers or recommendations, and a dedicated scraper for one known page or platform.

Prepare the request

Read deepapi for credentials, headers, and shared protocol. Use POST /v1/scrape/deep with an API key scoped to scrape:deep.

• query: required, 500 characters maximum. Name one subject, add identifying context, and state needed information; keep longer instructions for your synthesis.
• urls: optional public website/profile seeds to reduce namesake mistakes. They anchor discovery without limiting results to those URLs.
• sources: optional source-type filter, e.g. ["website", "github", "twitter"]. Omit for broad discovery. It filters types, not domains, and may exclude a seed's type.
• maxCostUsd: "0.50" default, "5.00" maximum per request. A spending ceiling, not a quoted charge; respect the total budget across calls.
• dryRun: true: previews the credit hold without scraping, charging, or returning a dossier. Omit dryRun or set false for the paid call.

Send only documented fields: there are no model, provider, depth, maxItems, outputSchema, or separate instructions controls. Asking for a fact in query does not guarantee discovery or add a response field.

For unclear schema, pricing, scope, or availability, fetch GET /v1/capabilities?capability=scrape.deep; its live contract takes precedence.

Start and preserve request identity

Requires curl, jq, and uuidgen. Adapt the body. Load credentials from your configured secure source only when setup variables are missing; never source unrelated shell configuration or print the key.