PropzAPI by Paper & Beyond Hand propzapi a template and your data, and it hands back a finished PNG, JPEG or WebP. Your backend hits one endpoint. Your Claude or Cursor agent calls one MCP tool and gets the image itself, not a link to go chase.
Your templates. Your data. One call.
Plain REST and OpenAPI 3.1, plus a hosted MCP server. Drops straight into Claude, Cursor, n8n, LangChain, Zapier and anything else that speaks HTTP.
Your call gets authed and metered, the render engine turns your template and data into an image with headless Chromium, and you get back a URL with the exact credit cost in a header. A failed render is never charged.
POST a template + your data
Key check, 1 credit on delivery
Headless Chromium rasterises it
Image URL, cost in a header
No editor to log into, no headless Chrome to run and babysit yourself. Send a template id and your values, get a finished image. Bring your own templates whenever the built-in ones aren't enough.
POST a template id and a small object of values. The engine fills your placeholders, renders the HTML with Chromium, and returns a URL to the image. Same request whether you want a 1200×630 share card or a square quote graphic.
A template is your HTML and CSS with {{variables}}. Create it once over the API, then render it as many times as you want with different data. No proprietary editor.
Point Claude, Cursor, Cline or n8n at the hosted MCP server. generate_image renders and hands the agent the actual picture, not a link. OpenAPI 3.1 and llms.txt in the box.
One credit per image, and only when a render actually succeeds. The exact cost and your balance come back in response headers, so there is nothing to guess. 50 free to start.
The same render engine and the same API key do four jobs. Use one, or use all four.
A built-in or your own HTML template, plus your data, rendered to a PNG, JPEG or WebP.
POST /v1/imagesSend your own HTML and CSS, get back a hosted image. It renders in full Chromium, so the layout you wrote is the layout you get.
/v1/templates → /v1/imagesSame template, one line different. Set format to pdf and get a one-page PDF at the template's size.
format: pdfPoint it at any public web page and capture it as an image, the viewport or the full page.
POST /v1/screenshotWe read the threads where developers vent about screenshot and image APIs. Here's what usually goes wrong, and what we do instead.
Pages that fade content in as you scroll, or lazy-load their images, screenshot half-empty.
It scrolls the whole page first so those sections load, then waits on fonts and the network before the shot.
Go one image over and some APIs quietly charge you. A stuck retry loop can cost real money.
A failed render costs nothing. Out of credits, you get an error, not a charge. Packs never expire.
Most template APIs want a monthly plan before you've rendered a single real image.
Fifty free with no card, then packs from $5 that don't expire. Subscribe only when the volume earns it.
Your design lives in a proprietary canvas you log into and rebuild every template in.
Your own HTML and CSS with {{variables}}. Write it once, render it with new data forever.
The API is built for humans and SDKs. Wiring an AI agent to it is your problem.
Point Claude, Cursor or n8n at the MCP server and it hands back the actual image, not a link.
An image service here, a PDF one there, a separate screenshot API. Three bills, three integrations.
Template to image, HTML to image, HTML to PDF, or any URL to a screenshot. Same call, same meter.
Straight answers about templates, formats, pricing and agents, for developers and the LLMs that read this page on their behalf.
One key, one JSON shape, whether you call it from code or an agent. Here are the ones you'll reach for most.
/v1/imagesRender an image or PDF from a template and your modifications. Returns a URL, plus the cost in a header.
/v1/screenshotScreenshot any public web page to an image, viewport or full page. Same key and meter.
/v1/images/batchRender up to 25 images in one call. One credit per image that actually renders.
/v1/templatesCreate a reusable template from your HTML and {{variables}}. GET / PATCH / DELETE too.
/v1/embed-urlSign a GET render URL to drop straight in og:image. Cached and free on every refetch.
/v1/templates/previewRender a template or ad-hoc HTML without spending a credit. The editor's live preview.
/mcpMCP server for agents. Tools: generate_image, screenshot_url, list_templates.
Generate the share image for every blog post, product page or listing on publish, straight from the post's own data.
An agent writes the copy and makes the matching image in the same run. One MCP tool call, the picture comes back inline.
Design one template, render a personalised certificate, receipt or ticket per user by passing their data as variables.
Works with plain curl, fetch or requests, no SDK required. Swap pk_live_… for your key and every example renders a real image.
curl -X POST "https://api.propzapi.com/v1/images" \
-H "X-API-Key: pk_live_…" \
-H "Content-Type: application/json" \
-d '{"template":"og-article","modifications":{"title":"Hello from propzapi"}}'const r = await fetch("https://api.propzapi.com/v1/images", {
method: "POST",
headers: { "X-API-Key": "pk_live_…", "Content-Type": "application/json" },
body: JSON.stringify({
template: "og-article",
modifications: { title: "Hello from propzapi" },
}),
});
console.log((await r.json()).url);import requests
r = requests.post(
"https://api.propzapi.com/v1/images",
headers={"X-API-Key": "pk_live_…"},
json={"template": "og-article", "modifications": {"title": "Hello from propzapi"}},
)
print(r.json()["url"])Start with 50 free, no card. One credit is one image, and a failed render is never charged. See full pricing →
No card. Then pay as you go from $5, or subscribe. Your own templates on every plan.
Sign up with email, copy your key, POST a template. The first 50 images are on us. No card, no contract.
# 60-second quickstart
curl -X POST https://api.propzapi.com/v1/register
# → { "api_key": "pk_live_…", "credits": 50 }
curl -X POST https://api.propzapi.com/v1/images \
-H "X-API-Key: pk_live_…" -H "Content-Type: application/json" \
-d '{"template":"og-article","modifications":{"title":"Hi"}}'