Rendering APIs
Rendering APIs that remove consent walls, sign-in modals and paywall overlays before they capture. Screenshots and PDFs, one key, one quota. We measured the gap most APIs do not quote: 93% of renders succeed, 69% are usable.
Same browser, same page, same overlay suppression — only the last step differs. One key, one quota, one subscription: a PDF and a screenshot each cost one render.
Screenshot API
PNG, JPEG or WebP of any page, with whatever was covering it taken off first. Viewport or full page, retina, dark mode, signed URLs you can drop straight into an img tag.
POST /v1/render
→ image/png
93% succeed · 69% usable · ~2s median
HTML to PDF API
The same page printed rather than photographed. A3 through tabloid, landscape, margins, scale, page ranges and page numbers — on the key and the allowance you already have.
POST /v1/pdf
→ application/pdf
theguardian.com: 1 page with the wall, 22 without
An agent that can see a page is more useful than one that cannot. Everything needed to discover and call both products without a wrapper:
/openapi.json OpenAPI 3.1, both endpoints/llms.txt plain-language summary for models/index.md this site as markdown/.well-known/api-catalog RFC 9727 catalog/.well-known/mcp/server-card.json MCP card — render_url and render_pdf/.well-known/ai-catalog.json ARD capability manifest/.well-known/agent-skills/index.json Agent Skills indexAsk any page for Accept: text/markdown and you get
the markdown rather than the chrome. An agent driving a browser that
supports WebMCP finds a render_url tool on this site without
needing a key at all.
Cached renders are free and never count against your quota. They cost us a disk read, so charging for them twice would be charging for nothing. One plan covers both products — a PDF and a screenshot each cost one render against the same allowance.
$0forever
100 / month
$9.99/ month
3,000 / month
$39.99/ month
20,000 / month
$99/ month
75,000 / month
Already subscribed? Manage your plan or cancel — no key needed, Stripe emails you a link.
Most of them return the page with the cookie banner still on it. We benchmarked a 29-URL corpus: 93% of renders technically succeeded, but only 69% were images you could actually use. Seven were ruined by consent overlays and exactly one by bot protection. Rendershed treats that gap as the product.
Never. It either declines, where a genuine reject control exists, or it hides the banner cosmetically, which consents to nothing. Reject buttons that actually lead to a paid subscription are detected and skipped.
Sometimes, and we do not claim otherwise. We measured headless, stealth and headful browsers from both residential and datacenter addresses: the browser makes no difference, the IP makes some, and a small number of sites are simply not renderable. Those return an error rather than an image of a challenge page.
Mint a signed URL with POST /v1/sign and use it as the src. The signature covers every parameter, so the URL cannot be edited into a different render, and your API key never reaches the browser.
Yes. Rendershed exposes an MCP server so an AI agent can render a page and look at it as part of a task, plus an OpenAPI description and llms.txt for discovery.
Yes, at POST /v1/pdf, and it runs on the same key, the same plan and the same monthly allowance — one PDF costs one render, and there is no separate PDF subscription. Overlay removal matters more for PDF than for images: a consent wall locks page scrolling, so the printable document stops at the fold. We measured theguardian.com printing as one page with the wall in place and twenty-two pages with it removed.
No. Calls without a key run on an anonymous tier of 40 renders an hour, metered against your address, so the examples on this page work when pasted. A free key raises that to 100 a month from anywhere; paid plans run $9.99 for 3,000, $39.99 for 20,000 and $99 for 75,000. Cached renders are free at every tier and never count against a quota.