Plans & credits
Every org is on a plan. The plan grants a monthly credit allotment and sets the org’s limits, and it clamps every request before it’s matched.
The catalog
Section titled “The catalog”| Basic | Pro | Enterprise | |
|---|---|---|---|
| Monthly credits | 5,000 | 100,000 | Custom |
| Max concurrency | 10 | 200 | 2,000 |
Plans are a fixed catalog (basic, pro, enterprise); the dashboard’s plan
page is generated from it. Enterprise credits are unlimited and negotiated.
How credits are spent
Section titled “How credits are spent”Billing is per operation, in whole credits — no bytes, no per-GB math:
| Operation | Credits |
|---|---|
| Any proxied request — and each crawled page | 1 |
| + JavaScript render (headless browser) | +5 |
| + Structured extraction | +1 |
So a plain fetch costs 1 credit; a rendered, extracted page costs 7. Render and extract belong to the Scrape API — a standard proxy request is always 1 credit.
Getting credits
Section titled “Getting credits”-
Monthly allotment — your plan grants its monthly credits automatically at the start of each cycle.
-
Credit packs — top up any time with a prepaid pack; packs never expire:
Pack Credits Price 5k 5,000 $16 100k 100,000 $83 500k 500,000 $333
When your balance hits zero, requests are refused until you top up or your next allotment lands.
What a plan clamps
Section titled “What a plan clamps”- Credit balance — every request debits credits; an empty balance stops traffic until it’s refilled.
- Allowed regions — a request targeting outside them is rejected with
403. An org can be restricted to, say, the EU only. - Max concurrency — the number of simultaneous in-flight requests. Exceeding
it returns
429. (A per-second burst guard sits well above this to catch runaway clients; concurrency is the real throughput knob.) - Default strategy — the routing strategy used when a request doesn’t specify one.
Per-org overrides
Section titled “Per-org overrides”Within plan limits, an org can carry overrides (e.g. a tighter default strategy or a narrower region allow-list) without changing plans. The effective config enforced on the request path is the plan merged with these overrides.
Concurrency
Section titled “Concurrency”In-flight requests are counted per org atomically, so the concurrency cap is
enforced consistently across every proxy instance. When you’re at the cap, new
requests get 429 until in-flight work drains.