# DynaPictures vs Layerre (slim)

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

- Full: https://www.anchorterminal.com/compare/dynapictures-vs-layerre.md (~4,100 tokens) · this version ~2,130 tokens · JSON https://www.anchorterminal.com/compare/dynapictures-vs-layerre.json · canonical https://www.anchorterminal.com/compare/dynapictures-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 DynaPictures's 43.2 (E), and leads in 4 of 7 scored categories. DynaPictures leads on payments & pricing. Both do design templates.

- DynaPictures: E 43.2, rank #1257 of 1510 · https://www.anchorterminal.com/tools/dynapictures.min.md
- Layerre: C 57.6, rank #789 of 1510 · https://www.anchorterminal.com/tools/layerre.min.md
- DynaPictures, good for Personalised images and PDFs per record, image URLs in emails and pages, and email countdown timers, for marketing teams in the EU. Ahead on Payments & pricing, 30 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 Schema & documentation, 87 against 82; Agent ergonomics, 69 against 45; Security & auth, 48 against 26; Maintenance & community, 78 against 4. Also Runs on your own machine.

| Category | DynaPictures | Layerre |
| --- | --- | --- |
| Reliability (16%) | 42 | 42 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 82 | 87 |
| Agent ergonomics (13%) | 45 | 69 |
| Security & auth (14%) | 26 | 48 |
| Payments & pricing (10%) | 30 | 25 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 4 | 78 |
| Transparency & trust (7%) | 63 | 63 |

| Fact (where they differ) | DynaPictures | Layerre |
| --- | --- | --- |
| Vendor | DynaPictures GmbH | Layerre |
| Hosted endpoint | `https://api.dynapictures.com` | `https://api.layerre.com/v1` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Licence | Closed service under the DynaPictures terms of use (revision 2/2026) | MIT for the MCP server. The Layerre API is a closed service under terms last updated 13 August 2026 |
| Tools exposed | none | 13 |
| MCP registry | not listed | `com.layerre/layerre` |
| Last release | none | 2026-10-29 |
| Popularity | none | 119 npm/wk |

Why the edge:
- Maintenance & community, Layerre +74: DynaPictures 4 (No changelog, release notes or dated API change was found, and the MCP server card gives version 1.0.0 with no date (0). No dated changes since 8 August (0). Support by email and contact form, not tested (4 of 15). Not in the official MCP registry and no API SDKs (0). No public package or repository (0). 0 + 0 + 4 + 0 + 0 = 4.); 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.)
- Agent ergonomics, Layerre +24: DynaPictures 45 (The MCP tool definitions weren't read (listing them needs a session), and llms.txt describes groups that include layer-by-layer design authoring, so the count is unknown. REST responses are small objects with image URLs (12 of 25). Template and generated-image listings, with no field selection documented (10 of 20). Errors are JSON with a `message` and documented statuses, without codes (12 of 20). Requests aren't idempotent, by the vendor's own note, though identical image URLs are served from cache without a credit (6 of 20). An Editor SDK for embedding the editor, and no API client SDKs (5 of 15). 12 + 10 + 12 + 6 + 5 = 45.); Layerre 69 (13 MCP tools (15 for 11 to 30), with no toolsets or read-only subset (15). Template and variant lists take `skip` and `limit`, and templates filter by `tag` and `q` and can leave out layers (16 of 20). 422 validation bodies and a JSON 429 with `retry_after` (17 of 20). Every tool is annotated, read tools with readOnlyHint and idempotentHint, updates idempotent, no tool destructive, and the server has no delete tool. The REST API has no idempotency keys for variant creation (16 of 20). Few required fields, but no official SDK; a Postman collection and the MCP package only (5 of 15). 15 + 16 + 17 + 16 + 5 = 69.)
- Security & auth, Layerre +22: DynaPictures 26 (One API key per user with the user's full access, not limited to workspaces or actions; a new key is requested by email to support, with no rotation in the account (10 of 30). No read-only mode, and the MCP server can author and change designs (3 of 20). Tools return the account's own templates and renders; image layers accept outside URLs (10 of 15). A list of generated images, with no audit log documented (3 of 15). No security.txt, disclosure policy, bug bounty or certification found (0). 10 + 3 + 10 + 3 + 0 = 26.); 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.)
- Schema & documentation, Layerre +5: DynaPictures 82 (OpenAPI 3.1 at dynapictures.com/openapi.json with 20 paths (25). llms.txt, auth.md and an agent skill in Markdown (10). llms.txt says when to use the product and when it's a poor fit, and the skill gives call order for each job (17 of 20). Enums for formats and options, with layer overrides keyed by layer name (12 of 15). Request examples throughout and a status table in the skill, but the API reference's Errors section is unedited Slate template text about kittens (9 of 15). No URL version, additive changes, removals announced six months ahead with Deprecation and Sunset headers, and no changelog (9 of 15). 25 + 10 + 17 + 12 + 9 + 9 = 82.); 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.)
- Payments & pricing, DynaPictures +5: DynaPictures 30 (No x402, MPP or L402 (0). Image allowances per plan and AI credit packs ($20 for 1,000 credits) are public, but plan prices are filled in by the FastSpring script and weren't readable (10 of 20). Free plan and a 14-day trial with 30 API credits, no card (20). auth.md says a person has to copy the key; there is no OAuth or programmatic key (0). 0 + 10 + 20 + 0 = 30.); 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.)