Pricing
Free. Capped. No card.
One plan, because there is one kind of user: someone who needs pages as data and does not want to think about it. The cap is what keeps it free.
Free
$0forever, per account
- 50,000 credits a day, resets 00:00 UTC, shared across your keys
- Any public page as HTML, text, Markdown or JSON from CSS rules
- JavaScript rendering with headless Chrome when you ask for it
- 7 site endpoints that return clean JSON, cached and shared
- Metadata endpoint: title, description, Open Graph, JSON-LD
- Site requests: ask for a site on the board, get an endpoint or a reason
What a credit buys
| Plain fetch | 1 credit |
|---|---|
| JavaScript render | 5 credits |
| Metadata | 1 credit |
| Site endpoint, fresh fetch | 1 credit |
| Site endpoint, from cache | 0 |
| Failure on our side | refunded |
Rendering costs more because it runs a real browser. Site endpoints cache results up to 30 days and tell you the age of what you got.
Limits
| Credits per day | 50,000 per account |
|---|---|
| Requests per minute | 60 per key |
| API keys | 5 per account |
| Timeout | up to 30 s |
| Response body | up to 5 MB |
| Extraction rules | up to 50 per request |
Numbers on this page are the same constants the API enforces; if they change here, they changed there.
What you do not get
No proxies, no CAPTCHA solving, no anti-bot bypass, no geotargeting, no crawler, no uptime guarantee. A site that blocks plain requests comes back as SITE_BLOCKED, the credit is refunded, and the board says "Not possible". If those are the features you need, the comparisons point you to services that sell them.
Questions
Is it really free? What is the catch?
Yes. Every account gets 50,000 credits a day, no card, no trial clock. The catch is the cap and the honesty: there are no proxies or CAPTCHA solving, one person runs it, and there is no uptime guarantee.
Will it stay free?
The plan is to keep a free tier. Free access may be converted to a paid service in whole or in part at any time; if that happens it is announced on this site before it takes effect, and the terms say so plainly.
What happens when I hit the daily cap?
Requests return 429 QUOTA_EXCEEDED until 00:00 UTC, when the counter resets. The cap is per account, across all your keys.
Do failed requests cost credits?
If the failure is on our side (rendering unavailable, an internal error, a site blocking us, or a parser breaking) the credit is refunded automatically. Timeouts and unreachable targets are charged, because the work was done.
Can I use it commercially?
Yes, within the terms: lawful targets, no reselling as a competing hosted service, keep your keys secret.
I need more than the cap.
Say so on the board with what you are building. The caps exist so the service can stay free; they are not a sales funnel.
The legal version of all this is in the terms. Questions: the board.