How credits are consumed across scrape, map, and crawl flows in the managed cloud.
| Operation | Credit cost |
|---|---|
scrape | 1 credit |
map | 1 credit |
crawl start | 1 credit |
crawl polling | New pages discovered since the previous poll |
The crawl start reserves the job. Subsequent polls charge only for newly materialized pages, not for the total accumulated page count each time.
That prevents the same already-seen pages from being charged again and again just because you are checking progress.
| Scenario | Credit effect |
|---|---|
One scrape request | 1 credit |
One map request | 1 credit |
| Start one crawl job | 1 credit |
| Poll a crawl and receive 7 new pages | 7 additional credits |
| Poll again with no new pages | No new page credits |
The billing logic is designed to avoid charging you for requests that never become real usable work. Validation failures and certain upstream failures are refunded rather than treated like successful paid execution.
The safest way to confirm actual consumption is still the balance endpoint before and after a test.
Use GET /api/v1/account/balance with your API key to inspect included credits, purchased balance, and total available credits.