Credits and billing
You pay per answered request, in credits. A request the target did not answer costs nothing.
What one request costs
| Situation | Credits |
|---|---|
| The target answered, response up to 1 MB | 1 |
Each further megabyte started (by bytes.down) | +1 |
fresh_ip was requested | +5 |
| Timeout, unreachable target, TLS failure, too many redirects | 0 |
| Our own errors, busy pool, maintenance | 0 |
| Rejected before sending (invalid input, blocked target, limits) | 0 |
"Answered" means the target sent an HTTP response, whatever its status: a 404 or a 500 from the target is charged like a 200. Redirects that we follow are part of the same request.
A 2.4 MB download therefore costs 3 credits, and a small page fetched with a fresh IP costs 6.
Plans
| Plan | Price for 30 days | Requests included | At the same time | Per second | Largest response | Timeout | Extra per 1,000 |
|---|---|---|---|---|---|---|---|
| Free | €0 | 1,000, once | 1 | 1 | 2 MB | 30 s | not available |
| Starter | €19 | 25,000 | 5 | 5 | 5 MB | 60 s | €1.20 |
| Growth | €59 | 100,000 | 20 | 20 | 10 MB | 90 s | €0.90 |
| Scale | €199 | 500,000 | 50 | 50 | 25 MB | 120 s | €0.60 |
A plan is bought in the dashboard for 30 days at a time and does not renew by itself. Buying again, the same plan or another one, starts a new 30 days with full credits; credits left over are not carried over. When the 30 days end without a new purchase, the account returns to the free plan.
When the credits run out
Requests stop with credits_exhausted (402). With an active paid plan you can buy extra requests in the dashboard, in blocks of 5,000 to 100,000 at your plan's extra price. They are added to the running 30 days at once and expire with them. The one-time allowance of the free plan is not refilled.
Check your balance
Every response carries cost.credits_used and cost.credits_included. GET /v1/account returns the same figures without sending a request. See Account and usage.