# Pixelixe vs Templated API + MCP

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

- Canonical: https://www.anchorterminal.com/compare/pixelixe-vs-templated
- Markdown: https://www.anchorterminal.com/compare/pixelixe-vs-templated.md (~4,750 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 Pixelixe's 37.3 (F), and leads in every scored category. Both do design templates.

- Pixelixe: grade F, 37.3/100, rank #1355 of 1486. Markdown https://www.anchorterminal.com/tools/pixelixe.md · JSON https://www.anchorterminal.com/api/v1/tools/pixelixe.json
- Templated API + MCP: grade C, 58.8/100, rank #726 of 1486. 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

### Pixelixe (F)

Good for: Template fills and white-label editing for marketing and SaaS teams, with a JSON-to-graphic route for agents.

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

Watch for: Every error is HTTP 400 with a free-text message, including wrong keys and exhausted credits

### 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 15
- Schema & documentation, 74 against 66
- Agent ergonomics, 70 against 49
- Payments & pricing, 35 against 30
- Maintenance & community, 80 against 19
- Transparency & trust, 76 against 41

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 +61

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

### Reliability: Templated API + MCP +50

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

### Transparency & trust: Templated API + MCP +35

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

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

- Pixelixe (49): Seven compact MCP tools (25). Document and design-set search filters, with no pagination documented (10 of 20). All errors are 400 with free-text messages, so an agent can't branch on a code (6 of 20). No idempotency keys, and annotations couldn't be read on the closed server. The MCP tools only read and create, with nothing that deletes (5 of 20). Few required fields, but no official SDK (3 of 15). 25 + 10 + 6 + 5 + 3 = 49.
- 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.

### Schema & documentation: Templated API + MCP +8

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

### Payments & pricing: Templated API + MCP +5

- Pixelixe (30): No x402, MPP or L402 (0). Plan prices with monthly document counts are public, with no per-image price (10). 10-day trial with no card (20). A person signs up and copies the key, or approves OAuth in a browser (0). 0 + 10 + 20 + 0 = 30.
- Templated API + MCP (35): No x402, MPP or L402 in the docs or llms-full.txt (0). Plan prices and per-unit credit rules are public in pricing.md, 1 credit an image or PDF page and a pixel-rate formula for video (15). Trial of 50 credits with no card (20). A person signs up in a browser for a key or an OAuth login, including through Claude's connectors directory since 27 October 2026 (0). 0 + 15 + 20 + 0 = 35.

## Score by category

| Category | Weight | Pixelixe | Templated API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 15 | 65 | Templated API + MCP +50 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 66 | 74 | Templated API + MCP +8 |
| Agent ergonomics | 13% (16.2 this run) | 49 | 70 | Templated API + MCP +21 |
| Security & auth | 14% (17.5 this run) | 38 | 42 | Templated API + MCP +4 |
| 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) | 19 | 80 | Templated API + MCP +61 |
| Transparency & trust | 7% (8.8 this run) | 41 | 76 | Templated API + MCP +35 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **37.3 · F** | **58.8 · C** | |

## Facts side by side

| Fact | Pixelixe | Templated API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Pixelixe | Templated |
| Hosted endpoint | `https://studio.pixelixe.com/api` | `https://api.templated.io/v1` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Closed service under the Pixelixe terms of service (last modified 19 March 2026) | MIT |
| Tools exposed | 7 | 25 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `com.pixelixe/pixelixe-mcp` | `io.github.templated-io/mcp-server-templated` |
| Last release | 2026-03-26 | 2026-10-08 |
| Terms last updated | 2026-03-19 | 2026-01-10 |
| Privacy policy last updated | 2026-04-07 | 2026-09-08 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | 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

### Pixelixe

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

**Pixelixe.** Pixelixe's seven MCP tools and their LLM-oriented reference make template fills and JSON-to-graphic creation simple to call, with an OpenAPI file for the core endpoints. Every error comes back as a 400 with a message, there are no published rate limits, status page or changelog, and API access starts at $59 a month.

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

### Pixelixe

1. Call `pixelixe_search_documents` first to find the `document_uid` of the template to reuse
2. Use `pixelixe_generate_graphic_variant` to fill an existing template; it can't change the layout
3. Read the error `message` text, since every failure is a 400
4. Stop and tell the user on 'Not enough Credits'; retrying won't help
5. For a batch, use `pixelixe_create_multiple_images` and summarise counts rather than inlining every image

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

Templated API + MCP scores 58.8 (C) on agent readiness against Pixelixe's 37.3 (F), and leads in every scored category.

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

Both take an API key or an OAuth sign-in.

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

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


## For agents

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

## Other comparisons with Pixelixe or Templated API + MCP

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

---

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