CaptureKit alternative

A CaptureKit alternative with the billing rules written down

Both products cover capture plus extraction at an accessible price. The part worth comparing carefully is what counts as a billable unit, because that is the number that shows up twelve invoices from now.

See the numbers Start with 100 free captures

Stay where you are if

Their published table is lower for your volume — at 10,000 captures with few repeats, it is.

Move here if

What decides it is the billable unit: one successful, non-cached capture, defined in writing and reconcilable against your usage counter.

What moving looks like: Change the base URL and key, map the extraction options, then compare a batch on three numbers: the artifacts, the errors and the usage counter it moved.

capturekit alternative · request and resultPAGECAPTURE / 01

The same job, in our contract

curl -G https://api.pagecapture.dev/v1/take \
  -H "X-Access-Key: $PAGECAPTURE_KEY" \
  --data-urlencode "url=https://example.com" \
  -d "format=markdown" \
  -d "response_type=json" \
  -d "metadata_page_title=true" \
  -o page.json

Capture result

succeeded

https://example.com

Noma

Shop now

NEW COLLECTION

Objects for slower mornings.

Thoughtful essentials, made in small batches from natural materials.

Explore the collectionOur materials

No. 01 · Hinoki

PLANT-BASEDMADE IN SMALL BATCHESREFILLABLE

Artifact: PNG · 1440×900
Billing: 1 credit
Engine: stable

Extraction in the same request

Markdown, rendered HTML and page metadata come from the same capture, so text and image describe the same moment of the page.

The billable unit is defined

One successful, non-cached capture. Not a request, not an API call, not a page of output — and a multi-artifact job says how many it consumed.

Cache hits cost nothing

Scoped to your organization and keyed on the render spec, with options that do not change a pixel excluded from the key.

Open contract surface

OpenAPI 3.1, seven SDKs, an MCP server and an agent skill all speak the same public HTTP API. There is no parallel path that bills differently.

What this costs here

Priced on successful captures that miss cache

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
10,000 captures per month	8,820	Growth	$47.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.

What these vendors publish

CaptureKit, in their own numbers

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.

CaptureKit

Screenshot plus extraction and AI features at an aggressive price.

Free tier: 100 credits
10,000 credits: US$ 29 per month
50,000 credits: US$ 89 per month

Published by the vendor, checked 2026-08-14.

capturekit.dev

CaptureKit is trademarked by their respective owners and mentioned only to describe the comparison people are searching for. No affiliation is claimed.

Questions this raises

Is PageCapture affiliated with CaptureKit?

No. PageCapture is an independent product with its own implementation. CaptureKit is a trademark of its owner and is mentioned only to describe the comparison people are searching for.

Which one is cheaper?

It depends on your cache hit rate and failure rate, which is why both tables are on this page with their sources dated. At a steady mix with few repeats, their published table is lower at ten thousand captures.

Is it a drop-in replacement?

No. Map the documented contract, run both against your own fixtures and compare the artifacts, the errors and the resulting usage counters before moving traffic.

What is missing today?

Billing, which is the axis this page compares: checkout is not wired to a merchant of record yet, so procurement and tax handling are not in place. On the render side there is no managed proxy pool behind ip_country_code and no GPU pool behind request_gpu_rendering. If your migration depends on any of those, this is not the moment to move.

Screenshot API

A screenshot API that returns the file, not a job to poll

Screenshot API pricing

What a screenshot API costs when failures are free

HTML to image

Render your own HTML into an image

Run the page that breaks your current provider.

Open the playground