What bandwidth covers
Page-content extraction, fetch, bulk page items, monitor runs, and screenshots. Usage is based on compressed bytes, and cache hits cost half where supported.
Read bandwidth billing (opens in new tab)Every plan supports the same API. Monthly plans include bandwidth and credits, with lower top-up prices at higher volumes.
Cancel anytime.
PAY AS YOU GO
No subscription — pay only for what you use.
Pay-per-use after free balance.
STARTER
Prototypes and smaller workloads.
Eff. incl. $5.80 / GB · $5.80 / 1k cr
GROWTH
Production agents and monitoring.
Eff. incl. $3.96 / GB · $3.96 / 1k cr
SCALE
Large corpora and high volume.
Eff. incl. $2.79 / GB · $3.49 / 1k cr
Shared capabilities apply to every plan when the selected endpoint uses them — tiers differ only by usage allowances, rates, and concurrency, not by capture quality.
Page-content extraction, fetch, bulk page items, monitor runs, and screenshots. Usage is based on compressed bytes, and cache hits cost half where supported.
Read bandwidth billing (opens in new tab)Search and Schema extraction. Search is billed by result pages of credits; Schema uses a fixed credit charge per request plus the source-page bandwidth.
Read credit billing (opens in new tab)Illustrative · ongoing month · PAYG free balance excluded
Bandwidth is purchased per GB at the selected plan rate. Credits are purchased in 1,000-credit units at the selected plan rate.
See top-up details (opens in new tab)Auto-top-up is configured from the dashboard, together with the monthly cap on what it may spend. Unused bandwidth rolls over with no cap while you stay on your plan or move to a higher one; credits reset every billing period; top-ups expire 180 days after purchase.
See spending controls (opens in new tab)Markdown output bills at 1.5× the bytes fetched, and a scrape that asks forclean_markdown a further 3× on top of that. Cache hits cost half where supported. Failed zero-byte captures cost nothing.
clean_markdown and gets a successful clean adds 3× on top of its endpoint factor, so a cleaned Markdown scrape is billed at 4.5× the bytes fetched. Cache hits are billed at half the bandwidth where the endpoint supports caching, and captures that return zero bytes are not billed at all. Two charges survive a failure: a cached error reply is served from the cache and billed at the cache-hit rate, and a failed schema extraction refunds its credits but keeps the source page's bandwidth.At zero balance, a single request returns HTTP 402. There is no automatic overage; continuing requires a top-up. Bulk jobs pause, and monitor checks are skipped until balance is restored.
See exact balance behavior (opens in new tab)No. Pay as you go has no monthly fee — you are billed only for usage beyond the one-time free balance, at the PAYG rates.
No. The 50 MB of bandwidth and 100 credits are granted once when you start on PAYG, not refreshed each month.
Search is billed by result pages of credits. Schema uses a fixed credit charge per request plus the source-page bandwidth. Capture endpoints — scrape, fetch, screenshots, and monitor runs — are billed by bandwidth, and cache hits cost half where supported.
Unused bandwidth rolls over to the next month with no cap, for as long as you stay on your plan or move to a higher one. If you downgrade or cancel, your rolled-over bandwidth is frozen and stops being spendable: resubscribe at the same tier or higher within 90 days and it comes back in full, and after that it is gone for good. Credits do not roll over — they reset every billing period. If you cancel or lapse, any remaining purchased balance is held and unusable until you resubscribe at the same tier or higher, and purchased top-ups expire 180 days after purchase — a cancellation or downgrade resets that deadline to 90 days from the freeze, which can be sooner than the original.