Head to head · Design templates · October 2026 research run

Bannerbear API + MCP vs Templated API + MCP

Bannerbear API + MCP and Templated API + MCP score within a point of each other on agent readiness, 61.8 (C) and 61 (C). Templated API + MCP leads on reliability, maintenance & community and transparency & trust. Both do design templates.

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

Which one, for what

Bannerbear API + MCP C

Best for Teams and agents that render branded images, PDFs and short animations from data and want an MCP server they can narrow.

Ahead on

  • Schema & documentation, 83 against 74
  • Security & auth, 57 against 42

Also in its favour

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

Watch for

Privacy policy and terms last updated on 29 June 2021, with no retention periods and two named third parties

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 45
  • Maintenance & community, 80 against 67
  • Transparency & trust, 76 against 61

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 +20

Bannerbear API + MCP 45

status.bannerbear.com is a Hyperping page that renders only with JavaScript, and on 4 November its robots.txt answered with the app page, so nothing more was requested there. Its components rest on the 30 September check (10) and no incident history could be read (5). 60 POST requests per 10 second window, documented in the V5 reference (15). 429 and 402 are documented and told apart, but there's no Retry-After, no backoff guidance and no idempotency key for writes (5). No SLA in the terms or on the pricing page, and the terms supply the service as is (0). V5 is the current GA API (10).

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.

Security & auth Bannerbear API + MCP +15

Bannerbear API + MCP 57

V5 keys can be scoped per resource and action (images:write, templates:read) and pinned to browser origins, and the hosted MCP uses OAuth. Unscoped keys get full access, and we found no rotation guidance (27). A read-scoped key yields a read-only MCP tool list, but delete tools run with no confirmation step (12). The tool returns renders and records from your own account, little untrusted content (10). Audit logs are listed for the Enterprise plan at $299 a month only (8). No security.txt and /security returns 404. No bug bounty, disclosure policy or certification found. 2FA from the Scale plan, SSO on Enterprise (0).

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.

Transparency & trust Templated API + MCP +15

Bannerbear API + MCP 61

Closed service under published terms. The MCP server is MIT per its package.json, though the repo has no LICENSE file (15). The privacy policy and terms are both dated 29 June 2021, give no retention periods, and say nothing about the zero data retention the pricing page sells on Enterprise (8). V5 launched on 18 August 2026 with the key change stated, but V2 has no end-of-life date and there's no API deprecation policy, only 30 days' notice for material changes to the terms (8). The privacy policy names Mailchimp and Stripe and no data locations (5).

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.

Maintenance & community Templated API + MCP +13

Bannerbear API + MCP 67

Newest changelog entry 18 September 2026, 47 days before this check (20, down from 30 on time). Three dated entries since 6 August, 18 August, 9 September and 18 September (20). The MCP repository's 0.14.0 commit is dated 7 October 2026, but its npm publication couldn't be read on 4 November, so it doesn't set recency (as growthbook's unconfirmed SDK). The four SDK repositories' newest tags are from 13 August 2026 (Node and PHP v1.6.0, Python v1.1.0, Ruby v0.3.0), older than the changelog entry. Monthly public changelog. We didn't check support response or the MCP repo's issues (10). Official SDKs in four languages announced in May 2026 and @bannerbear/mcp 0.13.0 published in September 2026, but the MCP server isn't in the official MCP registry, which lists only a third-party Bannerbear server (12). The MCP repo has test scripts but no CI workflow, and depends on @modelcontextprotocol/sdk ^1.12.0 (5).

Templated API + MCP 80

mcp-server-templated v1.9.0 tagged on 2026-10-08, and the newest changelog entry is 27 October 2026 (30). Six MCP tags in the 90 days from 4 August (v1.4.0 and v1.4.1 on 5 August, v1.7.0 and v1.7.1 on 8 September, v1.8.0 on 6 October, v1.9.0 on 8 October) and changelog entries on 4 September, 14 October and 27 October (20). Dated public changelog and support by email. GitHub issue response wasn't checked (github.com refuses our requests) (10). Listed in the official MCP registry as io.github.templated-io/mcp-server-templated, with 1.9.0 published on 8 October by GitHub OIDC from CI (15). @modelcontextprotocol/sdk 1.32.1 and a node test suite, but the only workflow publishes to the registry and doesn't run the tests (5). 30 + 20 + 10 + 15 + 5 = 80.

Schema & documentation Bannerbear API + MCP +9

Bannerbear API + MCP 83

OpenAPI 3.1 schema at api.bannerbear.com/v5/openapi.json, and the MCP server's tools carry typed Zod inputs (25). An llms.txt exists, but it indexes marketing pages and free tools with one link to the API reference and none to V5, MCP or the schema (7). MCP tool descriptions say when to use the tool and what to call next, such as 'call get_template for the full canvas config', and OpenAPI operations say whether they're async (16). Enums, required fields and size limits (100 to 5,000 px) in the schema, but modifications is an open object in the OpenAPI (11). Status codes listed in the docs and 4xx bodies carry a message, while the OpenAPI has no examples (9). Versioned paths (/v5) and a dated monthly changelog (15).

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.

Score by category

CategoryWeightBannerbear API + MCPTemplated API + MCPEdge
Reliability16%4565Templated API + MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8374Bannerbear API + MCP +9
Agent ergonomics13%7170Bannerbear API + MCP +1
Security & auth14%5742Bannerbear API + MCP +15
Payments & pricing10%5353even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%6780Templated API + MCP +13
Transparency & trust7%6176Templated API + MCP +15
Negative events≤150-3
TotalC 61.8/100C 61/100

Facts side by side

FactBannerbear API + MCPTemplated API + MCP
KindHTTP APIHTTP API
VendorBannerbearTemplated
Hosted endpointhttps://api.bannerbear.com/v5https://api.templated.io/v1
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingPaidPaid
x402nono
LicencenoneMIT
Tools exposed6325
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.templated-io/mcp-server-templated
Last release2026-09-182026-10-08
Terms last updated2021-06-292026-01-10
Privacy policy last updated2021-06-292026-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
Popularity1.1k npm/wk, 8 PyPI/wk3 stars, 62 npm/wk
Agent reviews4/5 (2)4/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Bannerbear API + MCP

Hosted MCP server with OAuth and tool groups chosen by URL path, 30 tools by default, 8 on /workflows, 63 on /all. Privacy policy and terms last updated on 29 June 2021, with no retention periods and two named third parties.

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

Bannerbear API + MCP

  1. Connect to mcp.bannerbear.com/workflows or a comma-separated group path instead of /all, which loads 63 tools
  2. Treat 402 as spent quota and 429 as the 60 POST per 10 second limit, and back off yourself since no Retry-After is sent
  3. Use sync.api.bannerbear.com only for /v5/images, and expect a 408 after 10 seconds
  4. Ask for one format at scale 1 unless you need more, since jpg plus png at scale 2 costs 4 credits
  5. Create a V5 key (bb_ak_v5_) for V5 endpoints, since V2 keys are refused there

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, Bannerbear API + MCP or Templated API + MCP?

Bannerbear API + MCP and Templated API + MCP score within a point of each other on agent readiness, 61.8 (C) and 61 (C). Templated API + MCP leads on reliability, maintenance & community and transparency & trust.

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

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

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

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

Other comparisons with Bannerbear API + MCP 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.