# Bannerbear API + MCP vs Layerre (slim)

> Bannerbear scores 59.6 (C) to Layerre's 57.6 (C) for design templates. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/bannerbear-vs-layerre.md (~3,600 tokens) · this version ~1,580 tokens · JSON https://www.anchorterminal.com/compare/bannerbear-vs-layerre.json · canonical https://www.anchorterminal.com/compare/bannerbear-vs-layerre
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Bannerbear API + MCP scores 59.6 (C) on agent readiness against Layerre's 57.6 (C), and leads in 4 of 7 scored categories. Layerre leads on maintenance & community. Both do design templates.

- Bannerbear API + MCP: C 59.6, rank #693 of 1510 · https://www.anchorterminal.com/tools/bannerbear.min.md
- Layerre: C 57.6, rank #789 of 1510 · https://www.anchorterminal.com/tools/layerre.min.md
- Bannerbear API + MCP, good for Teams and agents that render branded images, PDFs and short animations from data and want an MCP server they can narrow. Ahead on Security & auth, 57 against 48; Payments & pricing, 35 against 25. Also Free to start without a card.
- Layerre, good for Bulk image and PDF variants from Canva designs a team already has. Ahead on Maintenance & community, 78 against 67.

| Category | Bannerbear API + MCP | Layerre |
| --- | --- | --- |
| Reliability (16%) | 45 | 42 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 87 |
| Agent ergonomics (13%) | 71 | 69 |
| Security & auth (14%) | 57 | 48 |
| Payments & pricing (10%) | 35 | 25 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 67 | 78 |
| Transparency & trust (7%) | 61 | 63 |

| Fact (where they differ) | Bannerbear API + MCP | Layerre |
| --- | --- | --- |
| Vendor | Bannerbear | Layerre |
| Hosted endpoint | `https://api.bannerbear.com/v5` | `https://api.layerre.com/v1` |
| Pricing | Paid | Freemium |
| Licence | none | MIT for the MCP server. The Layerre API is a closed service under terms last updated 13 August 2026 |
| Tools exposed | 63 | 13 |
| MCP registry | not listed | `com.layerre/layerre` |
| Last release | 2026-09-18 | 2026-10-29 |
| Terms last updated | 2021-06-29 | no date given |
| Privacy policy last updated | 2021-06-29 | no date given |
| Popularity | 1.1k npm/wk, 8 PyPI/wk | 119 npm/wk |
| Agent reviews | 4/5 (2) | none |

Why the edge:
- Maintenance & community, Layerre +11: 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).); Layerre 78 (@layerre/mcp-server 0.1.0 published to npm on 29 October 2026, 8 days before this check (30). MCP server commits from 19 to 24 October, the registry entry of 29 October, and What's New entries dated 21 August and 18 October in the sitemap (20). The repository is a week old with no issues to judge; support by email and in-app chat (5 of 25). com.layerre/layerre is in the official MCP registry under a domain-verified namespace (15). CI runs the vitest suite on push and pull requests to main on Node 22 (8 of 10). 30 + 20 + 5 + 15 + 8 = 78.)
- Payments & pricing, Bannerbear API + MCP +10: Bannerbear API + MCP 35 (No x402, MPP or L402 in the docs or the OpenAPI (0). Plans are public and the pricing page states credit costs per unit (1 credit per image per format and scale step, 2 credits a second of animation, 1 to 4 per media tool), between plan-only and per-unit pricing (15). Trial with 30 API credits and no card (20). A person signs up in a browser to get a key (0).); 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.)
- Security & auth, Bannerbear API + MCP +9: 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).); 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.)