CrawlVolt uses one commercial credit wallet and keeps the operational dimensions behind each debit visible in usage logs.
Measure the dimensions that create load.
- Scrape, Crawl and Map
- One credit for each successful page.
- Search
- Two credits per source and started batch of ten results, plus extracted pages.
- Browse
- Two credits per started browser minute.
- Telemetry
- Renders, actions, output bytes and session use remain visible without creating separate quotas.
Keep failures visible without pretending they were useful output.
CrawlVolt writes authenticated failures to the request log with a typed code, status, duration and request ID. That operations log is separate from successful billing usage.
Transient platform failures state whether retrying is appropriate. Client limits and invalid requests remain visible, but do not enter the successful-output ledger.
Return enough context to explain the invoice.
Create an API key or create an account before running the example. Replace your_api_key with the secret shown at creation.
export CRAWLVOLT_API_KEY="your_api_key"
curl https://www.crawlvolt.com/v1/usage \
-H "Authorization: Bearer $CRAWLVOLT_API_KEY"Read Errors and quotas for the credit rules and Cache and usage for the response fields. A cache hit still costs one credit. Use Pricing for current plan allowances.
The response exposes plan quotas, remaining units, cache hits, output-format totals, cost dimensions and the latest 50 authenticated calls from the last 30 days.
The developer console presents the same data, including trace copy and an incident-only filter.