Errors and quotas
Handle CrawlVolt request errors, retries, rate limits and account credit limits.
Failures use application/problem+json and include a stable code, HTTP status, request_id, retry guidance and billing metadata.
{
"type": "https://www.crawlvolt.com/errors/quota_exceeded",
"title": "quota_exceeded",
"status": 402,
"code": "quota_exceeded",
"detail": "the monthly credit quota for this account is exhausted",
"request_id": "req_01JWD8",
"retryable": false,
"billing": { "billable": false, "units": 0 }
}Retry 429, 502, 503 and 504 responses with exponential backoff and jitter. Do not automatically retry validation, authentication or scope failures.
Plan quotas
| Plan | Credits / month |
|---|---|
| Free | 1,000 |
| Developer | 5,000 |
| Pro | 25,000 |
| Scale | 100,000 |
| Plan | Requests / minute | Concurrent browser requests |
|---|---|---|
| Free | 30 | 2 |
| Developer | 120 | 5 |
| Pro | 300 | 10 |
| Scale | 600 | 25 |
All billable endpoints consume the same monthly credit wallet. /v1/scrape,
/v1/crawl, and /v1/map consume one credit per successful page. Search costs
two credits per source and started batch of ten results, plus extracted result
pages. /v1/browse costs two credits per started browser minute. Failed
requests release their reservation.
The response headers x-request-id and x-webdash-billable-units mirror the trace and committed units. x-ratelimit-limit, x-ratelimit-remaining, x-concurrency-limit and x-concurrency-active expose the current request controls. A rejected request returns 429, Retry-After and remains non-billable.
See Cache and usage for cache policy, cost telemetry and GET /v1/usage.