We turned the utilities you bookmark into endpoints.
PocketUtils is 9 web utilities — screenshots, PDFs, SSL audits, meta scans, link crawls — each one a documented REST endpoint. Free to try in your browser, paid in credits when you put it in a cron job.
Two halves of the same tool
Free online utilities stop at the browser. Developer APIs make you sign up before you can see whether the output is any good. Neither is a whole product.
The problem was never the tool
Free online utilities work fine. Finding one that is not buried in fake download buttons, that does not queue you behind an ad, and that you would be willing to point at a client's site — that is the hard part.
And they all stop at the browser
The moment you need the same conversion a thousand times, or on a schedule, the tool is useless. You are back to running headless Chromium yourself, on infrastructure you now have to maintain.
So both halves ship together
We built 9 endpoints and put a real playground in front of each one. Test it free, in the browser, against production. When it needs to be automated, the same route takes an API key.
Six rules we don't bend
Not values on a poster — decisions we have already made, that you can check us against on any endpoint.
A tool is an endpoint
Every utility on this site is the browser front-end of a REST endpoint. There is no separate 'pro version' of the API — the playground calls production.
Price what costs us money
A render boots Chromium; a meta scan does not. So one costs 2 credits and the other costs 1. Failed requests cost nothing, because they cost us nothing.
Hold as little as possible
Files are processed in memory and dropped. We log that a call happened and what it cost, never what was in it. The cheapest data to secure is data you never kept.
Latency is a feature
A utility API you have to wait on is really a batch job. We keep the render fleet warm and treat a slowdown as a bug to fix, not a tier to upsell.
Documented or it doesn't ship
Request and response schemas, error codes, rate-limit headers, and snippets in five languages. An undocumented endpoint is an unfinished one.
Boring on purpose
No dashboards you have to learn, no SDK you have to adopt, no webhook you have to host. It is HTTP, and it behaves the way HTTP is supposed to.
What we are, and what we are not
An independent product, small on purpose, funded by people paying for it rather than by advertising or by selling what passes through it.
Is there a free API tier?
No. The website is the free tier — every endpoint is fully testable in the browser before you spend anything. Automating it needs a plan.
Do you keep what I process?
No. Files and rendered output live in memory for the duration of the request. We record that a billable call happened, not what was in it.
Do you sell data or run ads?
No, and we do not intend to. Subscriptions and top-ups are the entire business model.
How big is the team?
Small and independent. That is why the endpoint list is short and each one is finished, rather than long and half-documented.
You already tested it. Now automate it.
Plans start at $9 for 5,000 credits — enough for 2,500 screenshots or 5,000 meta scans a month. Top up whenever a spike hits.
- Key issued the moment you subscribe
- Credits roll into every endpoint
- Cancel from the dashboard, any time