Can I put a Rendry image straight into og:image like Placid's URL API?

Yes. share_preset_url turns a template into a public GET link with no key and no backend; variables ride in the query string, repeats are served from cache and cost nothing.

Is Rendry cheaper than Placid?

The billing models differ more than the prices: Placid is a monthly subscription, Rendry sells one-time packs ($15 → 500, $35 → 2,500 credits) valid for a year. If you render steadily every month at high volume, a subscription can cost less per image; if your load is bursty or you are just starting, packs waste nothing.

Does Rendry have an MCP server too?

Yes, with 32 tools covering the whole loop: design the template, check a draft for 0.1 credits, render, and read back what fit. Placid ships an MCP server as well; its scope is filling variables in templates a human designed first.

A Placid alternative built for agents that cannot see the picture

Placid is a solid product from a small Austrian team and it has been shipping since 2018. Two things it does not do: tell the caller whether the text actually fit, and render more than one image per request. Both matter when the thing calling the API is an agent working unattended.

Start free; 50 credits included · Documentation

How the pricing models compare

Product	Pricing	Free start	Visual editor	Native MCP
Rendry	$35 one-time → 2,500 credits, valid 365 days; no subscription	50 credits on signup, no card	Full drag-and-drop	Native remote: the agent designs templates itself, drafts at 0.1 credit, text-fit metrics
Bannerbear	$49/mo subscription → 1,000 credits/mo	Trial: 30 credits	Yes	Community wrappers only
Placid	Subscription; Pro tier → 2,500 credits/mo (price on their page)	Trial (a few credits)	Yes	Official remote; render-only (fills human-made templates)
Templated	$29/mo billed annually → 1,000 credits/mo	Trial: 50 credits	Yes	Official; create/edit works, every visual check costs a paid credit

Competitor details as of 2026-08-14, from public pricing pages (sources: https://www.bannerbear.com/pricing/, https://placid.app/pricing, https://templated.io/pricing/). Their sites are authoritative for current numbers. All product names are trademarks of their respective owners; this comparison is informational, not an endorsement.

Why teams and agents use it

It tells you what got clipped. Placid's image response is {id, status, image_url, polling_url} — nothing about the render itself. Rendry returns text_fit per layer: requested size, size after auto-fit, and the actual drawn width and height against the box. An agent that cannot see the picture can still tell that the headline was shrunk from 64 to 44 px, or clipped outright. In batches this becomes a per-row verdict.
Ten items per call, not one. POST /images on Placid creates exactly one image; a thousand product cards means a thousand HTTP requests against a 60 req/min limit. render_batch takes up to 10 data sets per call and reports each row separately.
Cyrillic that does not break the layout. Russian words run 20-40% longer than their English equivalents, which is where fixed template boxes fail. Rendry hyphenates algorithmically and reports the result, instead of silently shrinking until something fits.
Packs instead of a subscription. Placid bills monthly and unused credits roll over only up to double your plan. Rendry sells one-time packs from $15 that stay valid for 365 days — pay for capacity, not for months. Signup includes 50 free credits, no card.
Multi-page PDF where the text stays text. A document is an ordered list of pages rendered as ONE file — invoices, certificates, catalogues — and the text in it is real text: searchable, selectable, copyable. dry_run names every layer that would be rasterized, and the page count and the price, before a single credit is spent.
Where Placid is still ahead, honestly. Video output, a 16 000 px canvas, and integrations with Zapier, Make, n8n, Airtable, Webflow and WordPress. If your workflow is no-code and lives in those tools, or you need MP4 out, Placid covers that today and Rendry does not.

Ready-made templates for this

OG Image — Product Launch: 1200x630 launch card. Dark green-cyan mesh, INTRODUCING eyebrow, glowing gradient product name. Mood: keynote moment. Use for: product/feature launches. (1200x630)
Product Card: 1080x1350 product card. Light pastel mesh, product photo with soft shadow, red circle discount badge, gradient price, dark CTA pill. Mood: clean marketplace. Use for: e-commerce listings, catalogs. (1080x1350)
Sale Banner: 1200x628 sale banner. Hot red-orange mesh + grain, giant gradient percent, tilted yellow badge, white CTA. Mood: loud urgency. Use for: sales, promos, flash deals. (1200x628)

Built for AI agents first

Rendry ships a native remote MCP server (https://rendry.io/api/v1/mcp) with 32 tools. Your agent designs the templates itself, previews drafts cheaply, then renders batches — nobody has to lay anything out by hand. Full control over every pixel stays with the agent, while a human can always open the same template in the visual editor and adjust it. No headless browser, no screenshot hacks, no glue code.

Machine-readable: llms.txt · llms-full.txt · openapi.json · mcp.json

Frequently asked questions

Can I put a Rendry image straight into og:image like Placid's URL API?: Yes. share_preset_url turns a template into a public GET link with no key and no backend; variables ride in the query string, repeats are served from cache and cost nothing.
Is Rendry cheaper than Placid?: The billing models differ more than the prices: Placid is a monthly subscription, Rendry sells one-time packs ($15 → 500, $35 → 2,500 credits) valid for a year. If you render steadily every month at high volume, a subscription can cost less per image; if your load is bursty or you are just starting, packs waste nothing.
Does Rendry have an MCP server too?: Yes, with 32 tools covering the whole loop: design the template, check a draft for 0.1 credits, render, and read back what fit. Placid ships an MCP server as well; its scope is filling variables in templates a human designed first.