Pricing and limits
What a Grabber API request costs, when you are charged, how prepaid credit works, and the rate, size and time limits of every request.
Last updated
What it costs
Grabber is prepaid. A fetch costs $0.001, or $0.005 with
js_render=true. You pay only for a page that was loaded: any error
costs nothing. A page whose own server answered 404 or 500 is still a loaded
page, so it is a 200 and it is charged. Read data.fetch.httpStatusCode.
Every answer that got as far as billing carries X-Grabber-Cost (what this
request cost, in USD) and X-Grabber-Balance (what is left). With
unwrap=true the body is the content itself with no envelope, so these headers
are the only place the spend is reported.
Prices
| Item | Price |
|---|---|
| A page | $0.001 |
A page with js_render=true | $0.005 |
| Any error | $0 |
| Credit when you sign up | $1, about 1,000 pages |
| Smallest top-up | $5 |
| Credit lifetime | 365 days from when you add it |
Credit
Grabber is prepaid, with no plan or subscription. Add credit in the dashboard, from $5; the presets are $10, $25, $50, $100. You pay by card through Stripe, and Grabber pays Stripe's fee, so every dollar you pay becomes a dollar of credit.
With auto top-up, your saved card is charged when the balance falls below a level you choose, $5 unless you change it, and $25 of credit is added. Credit is valid for 365 days after you add it.
Limits
60 requests per minute per key. Every request with a valid key counts,
including one refused for a bad query or for lack of credit. Over the limit the
answer is 429 with a Retry-After header.
A rendered fetch (js_render=true) can take up to 120 seconds. Use a client
timeout of at least 130 seconds.
| Limit | Value |
|---|---|
| Requests per minute, per key | 60 |
Length of url | 8,192 characters |
| Size of the page | 8 MiB |
| Time for a rendered page | Up to 120 seconds |
| Suggested client timeout | 130 seconds |
| Methods | GET only |

