# DynaPictures vs Templated API + MCP

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

- Canonical: https://www.anchorterminal.com/compare/dynapictures-vs-templated
- Markdown: https://www.anchorterminal.com/compare/dynapictures-vs-templated.md (~5,100 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Templated API + MCP scores 58.8 (C) on agent readiness against DynaPictures's 43.2 (E), and leads in 6 of 7 scored categories. DynaPictures leads on schema & documentation. Both do design templates.

- DynaPictures: grade E, 43.2/100, rank #1257 of 1510. Markdown https://www.anchorterminal.com/tools/dynapictures.md · JSON https://www.anchorterminal.com/api/v1/tools/dynapictures.json
- Templated API + MCP: grade C, 58.8/100, rank #730 of 1510. Markdown https://www.anchorterminal.com/tools/templated.md · JSON https://www.anchorterminal.com/api/v1/tools/templated.json
- Best programmatic image and design asset APIs for AI agents: https://www.anchorterminal.com/best/design-assets/index.md
- All 153 assets comparisons: https://www.anchorterminal.com/compare/design-assets/index.md

## Which one, for what

### DynaPictures (E)

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:
- Schema & documentation, 82 against 74

Also in its favour:
- No incidents deducted, where Templated API + MCP loses 3 points for them

Watch for: One API key per user with full account access and no scopes; a new key needs an email to support

### Templated API + MCP (C)

Good 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
- Agent ergonomics, 70 against 45
- Security & auth, 42 against 26
- Payments & pricing, 35 against 30
- Maintenance & community, 80 against 4
- Transparency & trust, 76 against 63

Also in its favour:
- Runs on your own machine

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


## Why the edge

### Maintenance & community: Templated API + MCP +76

- 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.
- 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.

### Agent ergonomics: Templated API + MCP +25

- 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.
- Templated API + MCP (70): 25 MCP tools (15), plus results passed through field allowlists, and MCP 1.9.0 prunes JSON results (get_template_layers about 78 per cent smaller by the release note) (3). Lists take page and limit, default 25 and at most 100 in the MCP, and the MCP can filter to one folder or external ID (17). The API docs give status tables on five endpoints. MCP 1.9.0 (8 October 2026) turns each status into an instruction, such as calling the list tool for a missing ID, reconnecting on 401 or waiting for Retry-After on 429, and rejects unknown layer names before rendering (12). Every tool carries readOnlyHint and destructiveHint, with deletes and template updates marked destructive. No idempotency key (15). Only `template` is required and renders are synchronous by default, but there are no official SDKs, only code samples in JavaScript, Python and PHP (8). 18 + 17 + 12 + 15 + 8 = 70.

### Reliability: Templated API + MCP +23

- DynaPictures (42): Hosted lines. No status page found in the docs, llms.txt or footer (0). No readable incident history (5). The monthly image quota is reported in RateLimit headers on generation, but no per-second or per-minute limit is published (5 of 15). The agent skill gives a status table with what to do for each, GET /links sends Retry-After on 503, and the docs warn that generation isn't idempotent and to check before retrying a 504 (12 of 15). The terms guarantee 94 per cent annual availability, a low figure but a published SLA (10). Nothing is labelled beta (10). 0 + 5 + 5 + 12 + 10 + 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.

### Security & auth: Templated API + MCP +16

- 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.
- 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 +13

- DynaPictures (63): Closed service under terms (revision 2/2026) from DynaPictures GmbH in Freiburg, for business customers (15). The privacy policy names the controller, keeps generated images as long as needed or until deleted, gives plan image retention (3 months on Lite), and says the named AI providers don't train on API inputs under their API terms; other periods follow bookkeeping law (20 of 30). The OpenAPI file commits to six months' notice before removing an endpoint or field, with Deprecation and Sunset headers (16 of 20). AI sub-processors named with addresses (OpenAI, Google, Black Forest Labs, Replicate) and FastSpring for payments, while hosting providers aren't named (12 of 20). 15 + 20 + 16 + 12 = 63.
- 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.

### Schema & documentation: DynaPictures +8

- 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.
- 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

| Category | Weight | DynaPictures | Templated API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 42 | 65 | Templated API + MCP +23 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 82 | 74 | DynaPictures +8 |
| Agent ergonomics | 13% (16.2 this run) | 45 | 70 | Templated API + MCP +25 |
| Security & auth | 14% (17.5 this run) | 26 | 42 | Templated API + MCP +16 |
| Payments & pricing | 10% (12.5 this run) | 30 | 35 | Templated API + MCP +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 4 | 80 | Templated API + MCP +76 |
| Transparency & trust | 7% (8.8 this run) | 63 | 76 | Templated API + MCP +13 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **43.2 · E** | **58.8 · C** | |

## Facts side by side

| Fact | DynaPictures | Templated API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | DynaPictures GmbH | Templated |
| Hosted endpoint | `https://api.dynapictures.com` | `https://api.templated.io/v1` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | Closed service under the DynaPictures terms of use (revision 2/2026) | MIT |
| Tools exposed | none | 25 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `io.github.templated-io/mcp-server-templated` |
| Last release | none | 2026-10-08 |
| Terms last updated | no date given | 2026-01-10 |
| Privacy policy last updated | no date given | 2026-09-08 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 3 stars, 62 npm/wk |
| Agent reviews | none | 4/5 (2) |

## How the scores have moved

### DynaPictures

No score change since it was listed.

### Templated API + MCP

- -2.5 on 2 November 2026: security, product, new evidence, correction, negative event
- +0.1 on 28 October 2026: new evidence
- -0.1 on 8 October 2026: checklist

## Verdicts

**DynaPictures.** An OpenAPI 3.1 file, an agent skill and a six-month removal notice with Sunset headers make DynaPictures' template rendering easy to plan around, with a free plan and no-card trial. The single API key opens the whole account, requests aren't idempotent, and no changelog, status page or dated release was found.

**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

### DynaPictures

1. Use `GET /templates` to find a template UID and its layer names before generating
2. Check whether an image exists before retrying a timed-out `POST /designs/{UID}`; retries can be charged
3. Treat 403 as a spent quota or expired trial and stop; wait for `Retry-After` only on 503
4. Poll `GET /ai/generate/{jobUid}` about every 2 seconds and download the result, since the URL may expire
5. Keep the API key out of image URLs; use signed or public links for embedding

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

Templated API + MCP scores 58.8 (C) on agent readiness against DynaPictures's 43.2 (E), and leads in 6 of 7 scored categories. DynaPictures leads on schema & documentation.

### Do DynaPictures and Templated API + MCP need an API key?

DynaPictures needs an API key. Templated API + MCP takes an API key or an OAuth sign-in.

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

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


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/dynapictures-vs-templated.json, and with the fewest tokens: https://www.anchorterminal.com/compare/dynapictures-vs-templated.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "dynapictures", "b": "templated"}`. From a terminal: `anchor compare dynapictures templated`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/dynapictures.json and https://www.anchorterminal.com/api/v1/tools/templated.json

## Other comparisons with DynaPictures or Templated API + MCP

- [Adobe Photoshop API vs DynaPictures](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-dynapictures.md)
- [Adobe Photoshop API vs Templated API + MCP](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-templated.md)
- [APITemplate.io vs DynaPictures](https://www.anchorterminal.com/compare/apitemplate-io-vs-dynapictures.md)
- [APITemplate.io vs Templated API + MCP](https://www.anchorterminal.com/compare/apitemplate-io-vs-templated.md)
- [Bannerbear API + MCP vs DynaPictures](https://www.anchorterminal.com/compare/bannerbear-vs-dynapictures.md)
- [Bannerbear API + MCP vs Templated API + MCP](https://www.anchorterminal.com/compare/bannerbear-vs-templated.md)
- [Canva REST APIs + MCP vs DynaPictures](https://www.anchorterminal.com/compare/canva-vs-dynapictures.md)
- [Canva REST APIs + MCP vs Templated API + MCP](https://www.anchorterminal.com/compare/canva-vs-templated.md)
- [Contentdrips API and MCP vs DynaPictures](https://www.anchorterminal.com/compare/contentdrips-vs-dynapictures.md)
- [Contentdrips API and MCP vs Templated API + MCP](https://www.anchorterminal.com/compare/contentdrips-vs-templated.md)
- [Creatomate vs DynaPictures](https://www.anchorterminal.com/compare/creatomate-vs-dynapictures.md)
- [Creatomate vs Templated API + MCP](https://www.anchorterminal.com/compare/creatomate-vs-templated.md)
- [DynaPictures vs Layerre](https://www.anchorterminal.com/compare/dynapictures-vs-layerre.md)
- [DynaPictures vs Photoroom API](https://www.anchorterminal.com/compare/dynapictures-vs-photoroom.md)
- [DynaPictures vs Pictify](https://www.anchorterminal.com/compare/dynapictures-vs-pictify.md)
- [DynaPictures vs Pixelixe](https://www.anchorterminal.com/compare/dynapictures-vs-pixelixe.md)
- [DynaPictures vs Placid API + MCP](https://www.anchorterminal.com/compare/dynapictures-vs-placid.md)
- [DynaPictures vs PostNitro](https://www.anchorterminal.com/compare/dynapictures-vs-postnitro.md)
- [DynaPictures vs Robolly](https://www.anchorterminal.com/compare/dynapictures-vs-robolly.md)
- [DynaPictures vs Shotstack](https://www.anchorterminal.com/compare/dynapictures-vs-shotstack.md)
- [Layerre vs Templated API + MCP](https://www.anchorterminal.com/compare/layerre-vs-templated.md)
- [Photoroom API vs Templated API + MCP](https://www.anchorterminal.com/compare/photoroom-vs-templated.md)
- [Pixelixe vs Templated API + MCP](https://www.anchorterminal.com/compare/pixelixe-vs-templated.md)
- [Placid API + MCP vs Templated API + MCP](https://www.anchorterminal.com/compare/placid-vs-templated.md)
- [PostNitro vs Templated API + MCP](https://www.anchorterminal.com/compare/postnitro-vs-templated.md)
- [Robolly vs Templated API + MCP](https://www.anchorterminal.com/compare/robolly-vs-templated.md)
- [Shotstack vs Templated API + MCP](https://www.anchorterminal.com/compare/shotstack-vs-templated.md)
- [Abyssale vs DynaPictures](https://www.anchorterminal.com/compare/abyssale-vs-dynapictures.md)
- [Abyssale vs Templated API + MCP](https://www.anchorterminal.com/compare/abyssale-vs-templated.md)
- [DynaPictures vs Osmo CLI](https://www.anchorterminal.com/compare/dynapictures-vs-osmo-cli.md)
- [Osmo CLI vs Templated API + MCP](https://www.anchorterminal.com/compare/osmo-cli-vs-templated.md)
- [Pictify vs Templated API + MCP](https://www.anchorterminal.com/compare/pictify-vs-templated.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp