Credits

A request is routed across transport tiers automatically, and you are charged for the tier that succeeded. The tiers are checked in order, and the first one that applies determines the cost:

The structured extraction pass is the one cost that adds to the transport tier rather than replacing it, because it runs on top of whatever fetch produced the page. It costs 2 credits and applies whenever a schema is supplied.

So a stealth fetch with a schema pass costs 15 + 2 = 17 credits, and a plain static fetch with a schema pass costs 1 + 2 = 3.

Credits are sold at $1 per 1,000 credits, and each plan includes a monthly allowance. See pricing for the tiers.

Credits are consumed on successful delivery. A request that returns nothing usable is not billed.

The cost is computed and checked before any upstream work begins. If your balance cannot cover a request, it is refused up front with 402 rather than after a crawl has already run, so a request that fails on quota costs you nothing.

The 402 response includes the numbers you need to decide what to do next:

The single largest lever is the transport tier. Most pipelines escalate everything to stealth out of caution and pay 15× the static rate for pages that never needed it.

Two things help. First, only set stealth on targets that defend themselves. The tier is chosen per request, so a pipeline can escalate selectively. Second, cache: if a page is stable between runs, fetching it again costs the full credit price for data you already have.