# DynaPictures vs Pixelixe (slim)

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

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

DynaPictures scores 43.2 (E) on agent readiness against Pixelixe's 37.3 (F), and leads in 3 of 7 scored categories. Pixelixe leads on security & auth and maintenance & community. Both do design templates.

- DynaPictures: E 43.2, rank #1257 of 1510 · https://www.anchorterminal.com/tools/dynapictures.min.md
- Pixelixe: F 37.3, rank #1377 of 1510 · https://www.anchorterminal.com/tools/pixelixe.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 Reliability, 42 against 15; Schema & documentation, 82 against 66; Transparency & trust, 63 against 41.
- Pixelixe, good for Template fills and white-label editing for marketing and SaaS teams, with a JSON-to-graphic route for agents. Ahead on Security & auth, 38 against 26; Maintenance & community, 19 against 4.

| Category | DynaPictures | Pixelixe |
| --- | --- | --- |
| Reliability (16%) | 42 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 82 | 66 |
| Agent ergonomics (13%) | 45 | 49 |
| Security & auth (14%) | 26 | 38 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 4 | 19 |
| Transparency & trust (7%) | 63 | 41 |

| Fact (where they differ) | DynaPictures | Pixelixe |
| --- | --- | --- |
| Vendor | DynaPictures GmbH | Pixelixe |
| Hosted endpoint | `https://api.dynapictures.com` | `https://studio.pixelixe.com/api` |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Paid |
| Licence | Closed service under the DynaPictures terms of use (revision 2/2026) | Closed service under the Pixelixe terms of service (last modified 19 March 2026) |
| Tools exposed | none | 7 |
| MCP registry | not listed | `com.pixelixe/pixelixe-mcp` |
| Last release | none | 2026-03-26 |
| Terms last updated | no date given | 2026-03-19 |
| Privacy policy last updated | no date given | 2026-04-07 |
| Terms restrict automated access | not found in the text | yes |

Why the edge:
- Reliability, DynaPictures +27: 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.); Pixelixe 15 (Hosted lines. No status page found on the site or in the docs (0). No readable incident history (5). No rate limit is published; the terms only forbid circumventing them (0). No 429, Retry-After or backoff guidance. Every error, a wrong key and exhausted credits included, is a 400 with a message (0). No SLA found; the terms supply the service as is (0). API v2 is current and not labelled beta (10). 0 + 5 + 0 + 0 + 0 + 10 = 15.)
- Transparency & trust, DynaPictures +22: 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.); Pixelixe 41 (Closed service under terms of 19 March 2026 that choose French law but name no company (12 of 30). The privacy policy of 7 April 2026 keeps account data while the account is active and 'as long as reasonably necessary' after, with no periods, and says nothing about AI processing or training (10 of 30). V1 is marked deprecated in the docs with no dates or notice period (5 of 20). Processors are described only by category, with Google Analytics named, and data processed in France, the EEA and other vendor countries (5 of 20). 12 + 10 + 5 + 5 = 32.)
- Schema & documentation, DynaPictures +16: 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.); Pixelixe 66 (OpenAPI 3.1 (version 2.0.0) at pixelixe.com/pixelixe-openapi.json, but it covers four endpoints, authentication, document search, graphic automation and photo effects, and leaves out the JSON-to-graphic and image processing APIs (18 of 25). llms.txt exists but routes readers to marketing pages; the MCP reference is written for LLMs (7 of 10). The MCP reference says what each of the seven tools maps to, that `pixelixe_generate_graphic_variant` 'is not a free-form layout API', lists common mistakes and how to present outputs (17 of 20). The MCP layer documents canonical field names and refuses legacy aliases; the REST modifications are open structures keyed by element name (10 of 15). Request examples throughout, but errors are one table of message strings all returning 400 (8 of 15). /v2 paths and a deprecated V1, with no changelog (6 of 15). 18 + 7 + 17 + 10 + 8 + 6 = 66.)
- Maintenance & community, Pixelixe +15: 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.); Pixelixe 19 (No dated release or API change was found. The newest dated items are the MCP registry entry of 26 March 2026 and the privacy policy of 7 April 2026, more than 180 days before this check (0). No three dated changes since 8 August (0). No changelog. Support by email at inquiries@pixelixe.com, not tested (4 of 15). com.pixelixe/pixelixe-mcp is in the official MCP registry under a domain-verified namespace; there are no official SDKs (15). No public package or repository (0). 0 + 0 + 4 + 15 + 0 = 19.)
- Security & auth, Pixelixe +12: 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.); Pixelixe 38 (A bearer API key per account, plus a public key for the embedded editor. The MCP server accepts the key or an OAuth token from studio.pixelixe.com/oauth/mcp with one `pixelixe.mcp` scope. No key scopes, rotation or revocation documented (18 of 30). No read-only mode, though the MCP tools can't delete or change account settings (10 of 20). Tools return the account's own templates and renders (10 of 15). No audit log or per-call record documented (0). No security.txt, disclosure policy, bug bounty or certification found (0). 18 + 10 + 10 + 0 + 0 = 38.)