CrawlVolt
<- Field NotesOperations / 02 Aug 2026 / 7 min

Fair quotas for browser workloads.

A page render, ten browser actions and a large PDF do not create the same load. A useful billing model should make that difference visible.

Opaque credits make a simple pricing page, but they make incidents and cost regressions difficult to explain. CrawlVolt keeps commercial quotas and operational cost telemetry separate.

01

Measure the dimensions that create load.

Browser units
Fresh page renders that consume browser capacity.
Action units
Clicks, fills, scrolls and waits executed during browse.
Output units
Returned bytes across text, structured data, screenshots and PDFs.
Storage units
Session state created, updated and retained.
02

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.

Retry contract

Transient platform failures state whether retrying is appropriate. Client limits and invalid requests remain visible, but do not enter the successful-output ledger.

03

Return enough context to explain the invoice.

curl https://www.crawlvolt.com/v1/usage \\
  -H "Authorization: Bearer $CRAWLVOLT_API_KEY"

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.