How it works
A render in five plain steps. No account, no data left behind, and a free floor you can try right now without paying anything.
Pick an endpoint
Decide what you need back: a full-page screenshot (PNG), a print-quality PDF, or a structured scrape of the rendered page. All three run the same real headless Chromium — the page's JavaScript executes and the render settles before anything is captured, so you get what a person would actually see.
Buy a budget of task-units
You don't buy renders one at a time — you buy a budget of browser-task-units, and each render draws from it by the endpoint's weight. A screenshot or scrape draws 1 unit; a PDF draws 2. The order builder shows the live USDC price for any budget before you commit. Stay under the free floor and there's no payment step at all.
Pay once in USDC — or use the free floor
Each order gets its own single-use payment address. You send one USDC payment for exactly that budget, and your units are credited automatically the moment the payment confirms. No recurring charge, no card, no account, no wallet linking. You also get your account key — a long random string, the only identity we hold, and how you come back to your budget and history.
Render — safely, from the continent you choose
Call /v1/screenshot, /v1/pdf or /v1/scrape with your key and a target URL, and pick a region — Canada, Frankfurt or Singapore. Every URL, and every redirect and sub-resource the page pulls, is re-validated at connect time and refused if it points at a private or internal address. The browser cannot be tricked into reaching your intranet or a cloud metadata endpoint. See the API docs for the exact request shapes.
Keep the receipt — then we forget you
Every render returns an Ed25519-signed receipt you can verify against our public key: proof of the endpoint, the hashed target, the location and the units it cost — with no raw URL and no PII inside. We keep only that hashed metadata, never your URLs or the rendered bytes. The detail decays to a non-personal aggregate, and within a year everything — including your key — is erased. You keep the proof; we keep nothing about you.
What is a task-unit?
One clean unit runs the whole thing. A browser-task-unit is the cost of one light render. Your budget is a bucket of them, and each call draws its endpoint's weight — nothing more, nothing hidden.
A quick feel for what a budget buys (these are unit counts, not prices):
| Budget | Screenshots (×1) | PDFs (×2) | Scrapes (×1) |
|---|---|---|---|
| 100 units | 100 | 50 | 100 |
| 1,000 units | 1,000 | 500 | 1,000 |
| 10,000 units | 10,000 | 5,000 | 10,000 |
Want to see what a given budget actually costs? The order builder shows the live price as you choose. See the pricing page for how the rate works.
The free floor
The free floor isn't a locked demo — it's the same order form, in its zero-cost range. Order a small budget within the floor and it's credited directly, with no payment and no wallet at all.
It's meant for exactly what it sounds like: a real, honest test of a target and of SwarmBrowser itself, before you ever send a payment. When you need real volume, raise the budget and pay once for it.
Log-free, on purpose
SwarmBrowser is the strictest service in the family. It renders your page, hands back the result, and keeps essentially nothing.
There is no access log of the URLs you rendered and no copy of the bytes we produced. The only durable trace of a render is a compact row carrying the endpoint, a SHA-256 hash of the target, the region and the units it cost — enough to show you your own history and sign a receipt, and useless to anyone trying to reconstruct what you looked at. A per-task spend cap of 100 USDC sits on top as a safety ceiling, not a target.
Ready when you are
Start on the free floor — no payment, no account. Raise the budget whenever you need real volume.