Introduction
RenderKit turns any URL — or raw HTML — into a screenshot, a PDF, or clean markdown through a single REST API. Same auth header, same request shape, same response envelope across all three primitives. Built for developers and AI agents, priced to undercut the incumbents.
The three primitives
Every render is a POST to one of three endpoints. They share a common parameter set (navigation, waiting, auth, caching, delivery) and add their own format-specific options.
| Primitive | Endpoint | Returns | Credits |
|---|---|---|---|
| Screenshot | POST /v1/screenshot | PNG · JPEG · WebP (hosted URL) | 1 |
POST /v1/pdf | Print-grade PDF (hosted URL) | 2 | |
| Extract | POST /v1/extract | Markdown · text · HTML (inline) | 1 |
One meter
There is no per-primitive pricing. A screenshot, a PDF, and an extract all draw from the same credit balance — 1, 2, and 1 credits respectively. Cache hits and failed renders are never charged.
Base URL
All endpoints live under one host. There is no regional routing to configure.
https://api.renderkit.tech/v1/screenshotYour first render
Authenticate with the x-api-key header and send a JSON body. The only required field is url (or html).
curl https://api.renderkit.tech/v1/screenshot \
-H "x-api-key: $RK_KEY" \
-H "Content-Type: application/json" \
-d '{ "url": "https://stripe.com", "full_page": true }'Every successful render returns the same envelope: { success, data, message }, where data is a render object with a hosted url (or content for extract). See Responses for the full shape.
Where to go next
- [Quickstart](/docs/quickstart) — get a key and ship a render in 60 seconds.
- [Authentication](/docs/authentication) — keys, sandbox vs. live, rotation.
- [Screenshot](/docs/api/screenshot) · [PDF](/docs/api/pdf) · [Extract](/docs/api/extract) — the full API reference.
- [MCP server](/docs/mcp) — wire all three primitives into Claude or Cursor.