The unit that decides your bill is a successful, non-cached capture. Everything else — retries you did not ask for, timeouts, a page that answered 500 — costs nothing here, so the table below is smaller than the request count you send.
# 1. Capture. The response header carries the request id.
curl -G https://api.pagecapture.dev/v1/take \
-H "X-Access-Key: $PAGECAPTURE_KEY" \
--data-urlencode "url=https://example.com" \
-d "format=png" \
-D headers.txt -o page.png
# 2. Ask what that single request was charged.
REQUEST_ID=$(grep -i '^x-request-id:' headers.txt | tr -d '\r' | cut -d' ' -f2)
curl https://api.pagecapture.dev/v1/requests/$REQUEST_ID \
-H "X-Access-Key: $PAGECAPTURE_KEY"
# 3. Ask what the period looks like so far.
curl https://api.pagecapture.dev/v1/usage \
-H "X-Access-Key: $PAGECAPTURE_KEY"Thoughtful essentials, made in small batches from natural materials.
The ledger entry is written in the same transaction that marks the request succeeded. A failed capture cannot produce one — including when the failure is ours.
A repeat of the same render spec inside your own organization is served from cache and never charged. Pages you capture on a schedule get cheaper, not more expensive.
Overage is opt-in, billed in blocks of a thousand credits, and stops at the hard limit you set. Off by default, it simply refuses the request instead of growing the invoice.
GET /v1/usage returns the period counters, and every request reports its own billable status — so a monthly figure can be checked against the requests that produced it.
PNG, WebP, PDF, Markdown and HTML cost the same credit. A second engineer on the account costs nothing.
Every number in this table is computed from the published plans — failures and organization-scoped cache hits are removed before the plan is chosen, because they are not billable.
| Scenario | Billable successes | Smallest included plan | Published monthly price |
|---|---|---|---|
| 1,000 screenshots | 882 | Basic | $10.00 |
| 10,000 screenshots | 8,820 | Growth | $47.00 |
| 50,000 screenshots | 44,100 | Scale | $155.00 |
Assumes 10% cache hits and 2% failures. Change either assumption and the billable count changes with it — that is the point of charging for success.
These figures are quoted from each vendor's own pricing page, with the date we last checked it. They are not converted to our billing unit, because they do not measure the same thing.
A complete, developer-friendly specialist API for screenshots.
Published by the vendor, checked 2026-08-14.
screenshotone.comHigh-fidelity capture with an emphasis on evidence, compliance and specialist support.
Published by the vendor, checked 2026-08-14.
urlbox.comSimplicity and low cost on top of AWS Lambda.
Published by the vendor, checked 2026-08-14.
apiflash.comScreenshot plus extraction and AI features at an aggressive price.
Published by the vendor, checked 2026-08-14.
capturekit.devThese names are trademarked by their respective owners and mentioned only to describe the comparison people are searching for. No affiliation is claimed.
Run the page that breaks your current provider.
Open the playground