Synchronous requests
Sync requests block until the scrape completes and return the full result in a single HTTP response.Request structure
All scraper endpoints follow a consistentGET structure with query parameters:
Common parameters
Some scrapers accept additional parameters. See individual scraper pages for endpoint-specific parameters.
Country codes
The API supports country-specific routing. Common examples:US, GB, DE, FR, AU, CA, JP.
For region-specific behaviour, see Regional availability.
Response structure
All successful responses follow this base structure:Common response fields
Each scraper returns additional provider-specific fields. See the individual
endpoint documentation for full response schemas.
Request examples
Asynchronous requests
Async mode lets you submit a scrape and receive ajob_id immediately - without holding an open HTTP connection. The scrape runs in the background. Ideal for batch jobs, background workers, or any prompt that may take a long time.
Credits are deducted at submit time and restored automatically if every retry attempt fails.
Step 1: Submit the job
HTTP 202 with the job ID:
Step 2: Poll until done
GET /jobs/{job_id} - no authentication required.
Job status response
Jobs are retained for 24 hours. Failed scrapes are automatically retried up to 3 times before the job is marked
failed.
Common questions
Why are some requests slow?
Request latency depends primarily on the upstream AI provider’s response time (5–45 seconds depending on provider and query complexity). Settimeout up to 600 seconds for complex prompts.
Can I request from a specific country?
Yes - pass any ISO 3166-1 alpha-2 code viacountry. Note that some providers don’t support all countries. See Regional availability.