# Creatomate vs Layerre (slim)

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

- Full: https://www.anchorterminal.com/compare/creatomate-vs-layerre.md (~4,050 tokens) · this version ~2,030 tokens · JSON https://www.anchorterminal.com/compare/creatomate-vs-layerre.json · canonical https://www.anchorterminal.com/compare/creatomate-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)

Layerre scores 57.6 (C) on agent readiness against Creatomate's 49.6 (D), and leads in 5 of 7 scored categories. Creatomate leads on payments & pricing. Both do design templates.

- Creatomate: D 49.6, rank #1078 of 1486 · https://www.anchorterminal.com/tools/creatomate.min.md
- Layerre: C 57.6, rank #785 of 1486 · https://www.anchorterminal.com/tools/layerre.min.md
- Creatomate, good for Teams that render video, images and GIFs from templates or JSON and want an agent to draft templates and start renders through MCP. Ahead on Payments & pricing, 35 against 25.
- Layerre, good for Bulk image and PDF variants from Canva designs a team already has. Ahead on Schema & documentation, 87 against 53; Maintenance & community, 78 against 54; Transparency & trust, 63 against 52. Also Runs on your own machine.

| Category | Creatomate | Layerre |
| --- | --- | --- |
| Reliability (16%) | 40 | 42 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 53 | 87 |
| Agent ergonomics (13%) | 67 | 69 |
| Security & auth (14%) | 48 | 48 |
| Payments & pricing (10%) | 35 | 25 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 54 | 78 |
| Transparency & trust (7%) | 52 | 63 |

| Fact (where they differ) | Creatomate | Layerre |
| --- | --- | --- |
| Vendor | Creatomate | Layerre |
| Hosted endpoint | `https://api.creatomate.com/v2` | `https://api.layerre.com/v1` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Pricing | Paid | Freemium |
| Licence | Proprietary service under Creatomate's Terms and Conditions. The Node, PHP and Preview SDK libraries on GitHub are MIT | MIT for the MCP server. The Layerre API is a closed service under terms last updated 13 August 2026 |
| Tools exposed | 8 | 13 |
| MCP registry | not listed | `com.layerre/layerre` |
| Last release | 2026-09-19 | 2026-10-29 |
| Terms last updated | 2022-06-27 | no date given |
| Privacy policy last updated | 2022-06-27 | no date given |
| Popularity | 9 stars, 13k npm/wk | 119 npm/wk |
| Agent reviews | 3.3/5 (4) | none |

Why the edge:
- Schema & documentation, Layerre +34: Creatomate 53 (No OpenAPI file linked from the docs or llms.txt (0); the 8 October check of a guessed path on the API host is struck as a request to the product's API. The MCP tool schemas can't be read without an account. llms.txt with 50 Markdown topic links (10). Reference and topic pages state purpose and when to use `dry_run`, templates or raw RenderScript, with an out-of-scope page (16). Render options are typed with ranges and `status` is an enum, but `modifications` and `source` are open objects, and unknown names are ignored without an error (9). Examples in nine languages and a documented error body for 400, 401, 402, 404, 429 and 500 (13). `/v1` and `/v2` paths, no changelog (5). 0+10+16+9+13+5 = 53.); 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.)
- Maintenance & community, Layerre +24: Creatomate 54 (No changelog. Dated releases since 6 August are the n8n node 0.2.0 (11 August, per the 8 October npm reading), the rebuilt n8n node v1.0.0 (11 September) and v1.0.1 (19 September, a category metadata fix, half), and `@creatomate/preview` 1.6.1 (3 September, removing a dependency and type definitions from the build, half). The newest release that changes code is n8n v1.0.0, 54 days before the check (20). Three counted entries in 90 days (20, cause evidence; it drops to 0 after 9 November when 0.2.0 leaves the window). Support by email, no public changelog or forum found, and two open GitHub issues across the libraries per the 8 October check (5). The Node library was last tagged 1.2.1 on 23 September 2024 and calls `/v1`, the PHP library was last pushed on 21 October 2024, and the Preview SDK is current (7). No CI in the Node repository (2). 20+20+5+7+2 = 54.); 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.)
- Transparency & trust, Layerre +11: Creatomate 52 (Closed service under published terms, with MIT client libraries (15). Render retention of 30 days is stated the same way in the docs, pricing page and llms.txt. The privacy policy is dated 27 June 2022 with no retention period for personal data, no DPA was found, and the terms let Creatomate make user Content available to other users (12). No deprecation policy, and `/v1` and `/v2` are documented side by side with no dates (2). The privacy policy names Paddle, AWS, DigitalOcean, Google Analytics, Cloudflare and GitLab, with no data locations (8). Terms and privacy policy re-read on 4 November, both still dated 27 June 2022. 15+12+2+8 = 37.); 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.)
- Payments & pricing, Creatomate +10: Creatomate 35 (No x402, MPP or L402 (0). The pricing page now shows its plan prices in the page (Essential $540 a year for 2,000 credits a month, Growth from $1,290 a year for 10,000, Beyond from $3,290 a year for 50,000), the docs give $54 and $129 for the monthly Essential and Growth 10K, and the credit formula per image and per video is public. Credits come only inside monthly plans, with no per-credit price or top-up, so this sits between plan-only and per-unit pricing, as bannerbear, placid and templated are read (15, the earlier partial kept, see open questions). A free plan with 50 credits, no card and no time limit (20). A person signs up in a browser and copies a key or signs in through OAuth (0). 0+15+20+0 = 35.); 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.)