Head to head · Design templates · October 2026 research run

Layerre vs Templated API + MCP

Templated API + MCP scores 58.8 (C) on agent readiness against Layerre's 57.6 (C), and leads in 5 of 7 scored categories. Layerre leads on schema & documentation and security & auth. Both do design templates.

Best programmatic image and design asset APIs for AI agents · All 153 assets comparisons

Which one, for what

Layerre C

Best for Bulk image and PDF variants from Canva designs a team already has.

Ahead on

  • Schema & documentation, 87 against 74
  • Security & auth, 48 against 42

Also in its favour

  • No incidents deducted, where Templated API + MCP loses 3 points for them

Watch for

Imports Canva designs only; there is no template editor of its own

Templated API + MCP C

Best for Agents and SaaS builders who render images, PDFs and short MP4s from templates and want a well-behaved MCP server they can fence per customer.

Ahead on

  • Reliability, 65 against 42
  • Payments & pricing, 35 against 25
  • Transparency & trust, 76 against 63

Also in its favour

  • Free to start without a card

Watch for

One API key with full account access, and the MCP docs document it as ?apiKey= in the URL

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Templated API + MCP +23

Layerre 42

Hosted lines, for the REST API and the hosted MCP server. No status page found on the site, in llms.txt or in the docs (0). No readable incident history (5). Rate limits published as 10 requests a second, a 20-request burst and 600 a minute per IP address (15). A 429 carries Retry-After and a retry_after field, and the docs give retry code samples. No idempotency key or safe-retry note for variant creation, which spends renders (12 of 15). No SLA found (0). Neither surface is labelled beta, though both are at version 0.1.0 (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.

Templated API + MCP 65

Better Stack status page with API, App and Website components over 30, 60 and 90 days (20). The incidents page lists no incident for September, October or November 2026 and the RSS feed holds no entry, so the page has never posted one. This run scores a page that has never posted an incident 20, not the 30 of a clean record, and the page's own figure for the API is 100 per cent over 90 days (20). Rate limits per plan in the Markdown price list, 60, 150 and 300 requests a minute (15). No 429 behaviour, Retry-After or retry advice in the API docs or llms-full.txt. MCP 1.9.0 tells the model to wait and retry after a 429, which isn't API documentation (0). The pricing page lists "SLA & dedicated support" on the custom plan from $500 a month, with no SLA document or figure found (0). The render API is GA. Video launched on 7 January 2026 as "now live" (10). 20 + 20 + 15 + 0 + 0 + 10 = 65.

Schema & documentation Layerre +13

Layerre 87

Public OpenAPI 3.1 at layerre.com/openapi.json with 16 operations, and zod schemas on all 13 MCP tools in the open-source server (25). llms.txt, auth.md and Markdown mirrors of the pricing, FAQ and integration pages (10). Every operation has a description, and tool descriptions note costs such as 'an expensive operation that may take 10-30 seconds', without saying when not to use a tool (15 of 20). Layer properties have minimums, maximums and enums such as text_align, and list calls cap limit at 1,000 (14 of 15). 88 examples in the spec, and 404, 422 and 429 responses documented on most operations (13 of 15). Versioned /v1 paths and dated What's New pages, read from the sitemap since the pages are drawn by script; the API itself is version 0.1.0 (10 of 15). 25 + 10 + 15 + 14 + 13 + 10 = 87.

Templated API + MCP 74

No OpenAPI. All 25 MCP tools carry typed JSON Schema inputs, and server.json is published to the MCP registry, so partial credit (18). llms.txt, llms-small.txt, llms-full.txt, pricing.md and a Markdown version of every page (10). Some MCP descriptions guide the model well (update_template explains pages versus layers, create_render names get_template_layers first), others are one line (12). Format and layer type enums and a required template field, and MCP 1.9.0 caps list limits at 100 in the schema, but size, scale and fps limits sit in prose rather than min and max, and layers is an open object (10). Request and response examples per endpoint. Error tables with status codes appear on five endpoints (font, render, template and upload deletes and template update), none on create render (9). Versioned /v1 path, a dated changelog now at templated.io/changelog/ and tagged MCP releases (15). 18 + 10 + 12 + 10 + 9 + 15 = 74.

Transparency & trust Templated API + MCP +13

Layerre 63

The MCP server is MIT. The service is closed under terms of 13 August 2026 that name a sole proprietorship in Ontario (20 of 30). The privacy policy and DPA of the same date agree. Data is kept while the account is active and deleted from production on account deletion, with limited backups. Design files aren't used to train public AI models. Google Analytics runs on accepted cookies (24 of 30). No deprecation policy or notice period (0). Ten subprocessors listed with purpose and location in both documents, including Supabase, Stripe, Cloudflare, Google, Resend, Canva and Slack (20). 20 + 24 + 0 + 20 = 64.

Templated API + MCP 76

MCP server MIT with a LICENSE file. The rendering service is closed under published terms (18). Privacy policy updated 18 October 2026 with retention stated per data type (until you delete, files purged within 90 days of deletion, logs up to 90 days, billing records five years) and a DPA at templated.io/dpa, though it doesn't say whether customer content trains models (25). No deprecation policy or dated deprecation notices found (0). Subprocessors named by purpose, including Gemini, OpenAI, Anthropic and DeepSeek for AI functions, Photoroom for background removal, PostHog and Plausible for analytics and Stripe, Creem and Spedy for payments (18). 18 + 25 + 0 + 18 = 61.

Payments & pricing Templated API + MCP +10

Layerre 25

No x402, MPP or L402 (0). Plan prices are public with render counts, and one import or one variant is one render, so the price a render follows from the plan (about $0.03 on Starter, $0.005 on Pro) without being published per unit (15 of 20). Free plan of 50 renders a month with API access; the pricing page doesn't say whether a card is needed (10 of 20, half as with an unstated card rule). A person signs up and creates the key, or approves OAuth in a browser (0). 0 + 15 + 10 + 0 = 25.

Templated API + MCP 35

No x402, MPP or L402 in the docs or llms-full.txt (0). Plan prices and per-unit credit rules are public in pricing.md, 1 credit an image or PDF page and a pixel-rate formula for video (15). Trial of 50 credits with no card (20). A person signs up in a browser for a key or an OAuth login, including through Claude's connectors directory since 27 October 2026 (0). 0 + 15 + 20 + 0 = 35.

Security & auth Layerre +6

Layerre 48

OAuth 2.1 with PKCE for MCP through a Supabase authorisation server, and revocable lyr_ API keys with rotation in the dashboard. No scopes documented for either, and auth.md says the REST API has no OAuth yet (22 of 30). The MCP server cannot delete templates, change billing or manage API keys, but there is no read-only key or endpoint (12 of 20). Tools return the user's own templates and renders; template import fetches a Canva link the user gives (10 of 15). The open-source server emits audit log lines for each tool call for whoever runs it, and nothing per call is documented for the hosted service (4 of 15). No security.txt (the path returns the site's HTML shell), disclosure policy, bug bounty or certification (0). 22 + 12 + 10 + 4 + 0 = 48.

Templated API + MCP 42

The REST key has full account access by the docs' own words, and the privacy policy says it can be regenerated. The hosted MCP is an OAuth 2.1 resource server since MCP 1.6.0 (18). The MCP setup guide still documents ?apiKey= in the server URL for automations, less 10 (8). Folder and external ID scoping is enforced server side, and destructive tools are annotated so clients can ask first. No read-only key (12). Tool results pass through allowlists, and the docs describe server-side scoping as a guard against prompt injection (12). No audit log or per-call log found for the customer beyond the render list (3). A valid security.txt since 28 October 2026 (Last-Modified), sending reports to support@templated.io and expiring 8 October 2027, and 2FA since September 2026. No certification or bug bounty found (7, as a valid security.txt to a support address with nothing else). 8 + 12 + 12 + 3 + 7 = 42.

Score by category

CategoryWeight this runLayerreTemplated API + MCPEdge
Reliability16%204265Templated API + MCP +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28774Layerre +13
Agent ergonomics13%16.26970Templated API + MCP +1
Security & auth14%17.54842Layerre +6
Payments & pricing10%12.52535Templated API + MCP +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87880Templated API + MCP +2
Transparency & trust7%8.86376Templated API + MCP +13
Negative events≤150-3
TotalC 57.6/100C 58.8/100

Facts side by side

FactLayerreTemplated API + MCP
KindHTTP APIHTTP API
VendorLayerreTemplated
Hosted endpointhttps://api.layerre.com/v1https://api.templated.io/v1
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumPaid
x402nono
LicenceMIT for the MCP server. The Layerre API is a closed service under terms last updated 13 August 2026MIT
Tools exposed1325
Read-only variant documentednono
llms.txtyesyes
MCP registrycom.layerre/layerreio.github.templated-io/mcp-server-templated
Last release2026-10-292026-10-08
Terms last updatedno date given2026-01-10
Privacy policy last updatedno date given2026-09-08
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity119 npm/wk3 stars, 62 npm/wk
Agent reviewsnone4/5 (2)

How the scores have moved

Verdicts

Layerre

A public OpenAPI 3.1 contract, published rate limits with Retry-After, and 13 annotated MCP tools that can't delete anything make Layerre straightforward for an agent to call. It works only from Canva designs, is run by a sole proprietor with no status page or SLA, and its API and MCP server are at version 0.1.0.

Templated API + MCP

Templated's MIT-licensed MCP server has 25 tools, each annotated with readOnlyHint and destructiveHint, and can be fenced to one folder or customer. The REST key has full account access, the MCP docs still document it as ?apiKey= in the URL, and MCP 1.9.0 began rejecting calls 1.8.0 accepted with no notice.

Before you call either

Layerre

  1. Call layerre_auth_status first to confirm the connection
  2. Read a template's layer IDs with layerre_get_template before creating variants
  3. Use the bulk variant endpoint for batches; each variant still costs one render
  4. On 429 wait for the Retry-After seconds; limits are per IP address
  5. Expect template import from a Canva link to take 10 to 30 seconds

Templated API + MCP

  1. Call get_template_layers before create_render. MCP 1.9.0 rejects layer names the template doesn't have
  2. Set async true with a webhook_url for MP4, zip or batch renders, since zip without a webhook returns 400
  3. Video credits are width x height x fps x seconds / 50,000,000, so 10 seconds of 1080p at 30 fps costs 13
  4. Pass folderId or externalId on the MCP URL when one server serves several customers
  5. On a 429 wait for Retry-After when present and send batch calls one at a time. The API docs give no retry guidance

Questions

Which is better for AI agents, Layerre or Templated API + MCP?

Templated API + MCP scores 58.8 (C) on agent readiness against Layerre's 57.6 (C), and leads in 5 of 7 scored categories. Layerre leads on schema & documentation and security & auth.

Do Layerre and Templated API + MCP need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Layerre and Templated API + MCP without installing anything?

Yes. Layerre has a hosted endpoint at https://api.layerre.com/v1 and Templated API + MCP at https://api.templated.io/v1.

Other comparisons with Layerre or Templated API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.