# Creatomate vs Pixelixe

> Creatomate scores 49.6 (D) 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/creatomate-vs-pixelixe
- Markdown: https://www.anchorterminal.com/compare/creatomate-vs-pixelixe.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

Creatomate scores 49.6 (D) on agent readiness against Pixelixe's 37.3 (F), and leads in 6 of 7 scored categories. Pixelixe leads on schema & documentation. Both do design templates.

- Creatomate: grade D, 49.6/100, rank #1078 of 1486. Markdown https://www.anchorterminal.com/tools/creatomate.md · JSON https://www.anchorterminal.com/api/v1/tools/creatomate.json
- 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
- 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

### Creatomate (D)

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:
- Reliability, 40 against 15
- Agent ergonomics, 67 against 49
- Security & auth, 48 against 38
- Payments & pricing, 35 against 30
- Maintenance & community, 54 against 19
- Transparency & trust, 52 against 41

Watch for: No status page, incident history or SLA found. `status.creatomate.com` does not resolve

### Pixelixe (F)

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

Ahead on:
- Schema & documentation, 66 against 53

Also in its favour:
- Free to start without a card

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


## Why the edge

### Maintenance & community: Creatomate +35

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

### Reliability: Creatomate +25

- Creatomate (40): Hosted lines. No status page found. status.creatomate.com still has no DNS record and no page we read links to one (0). No readable incident history (5). 30 requests per 10 seconds per account, documented in the API reference for agents (15). The same page documents `X-RateLimit-*` headers on every response and `Retry-After` on 429 with "wait that long, do not retry immediately", but no idempotency key for renders, which are writes (10). The 8 October first-hand header reading came from a request to the product's API and is struck; the docs carry the same facts. No SLA found (0). The REST API and MCP server carry no beta label (10). 0+5+15+10+0+10 = 40.
- 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.

### Agent ergonomics: Creatomate +18

- Creatomate (67): Eight MCP tools on the vendor's list, re-read on 4 November, definitions unseen, and the template list omits sources (22). A `tags` filter on the template list, with no pagination, limit or render list found (6). The API reference documents a `hint` and a `documentation` URL on 400, 401, 404 and 429, a `hint` on 402 and 500, plus advisory `errors` and `warnings` and a free `dry_run` (20). No idempotency key. `dry_run` and status polling are safe, and template delete is now described as a soft delete that an open editor can restore; MCP annotations were not readable (8). `template_id` alone starts a render, and the Node and PHP libraries are official but last published in 2024 (11). 22+6+20+8+11 = 67.
- 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.

### Schema & documentation: Pixelixe +13

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

### Transparency & trust: Creatomate +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.
- 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.

### Security & auth: Creatomate +10

- Creatomate (48): MCP uses OAuth authorisation code with PKCE S256 and dynamic client registration, one scope, with connections revocable per application. REST uses one unscoped key per project, and key rotation is not documented (22). Each MCP connection reaches one project and a project can have a monthly credit budget, but there is no read-only mode and no server-side confirmation before a render or delete (8). Returns the account's own templates and renders (10). Account Settings lists MCP connections with last use, and the dashboard has an API log of renders (8). No security.txt, disclosure policy, bounty or certification found (0). No security.txt (404 on 4 November). 22+8+10+8+0 = 48.
- 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.

## Score by category

| Category | Weight | Creatomate | Pixelixe | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 40 | 15 | Creatomate +25 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 53 | 66 | Pixelixe +13 |
| Agent ergonomics | 13% (16.2 this run) | 67 | 49 | Creatomate +18 |
| Security & auth | 14% (17.5 this run) | 48 | 38 | Creatomate +10 |
| Payments & pricing | 10% (12.5 this run) | 35 | 30 | Creatomate +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 54 | 19 | Creatomate +35 |
| Transparency & trust | 7% (8.8 this run) | 52 | 41 | Creatomate +11 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **49.6 · D** | **37.3 · F** | |

## Facts side by side

| Fact | Creatomate | Pixelixe |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Creatomate | Pixelixe |
| Hosted endpoint | `https://api.creatomate.com/v2` | `https://studio.pixelixe.com/api` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Proprietary service under Creatomate's Terms and Conditions. The Node, PHP and Preview SDK libraries on GitHub are MIT | Closed service under the Pixelixe terms of service (last modified 19 March 2026) |
| Tools exposed | 8 | 7 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `com.pixelixe/pixelixe-mcp` |
| Last release | 2026-09-19 | 2026-03-26 |
| Terms last updated | 2022-06-27 | 2026-03-19 |
| Privacy policy last updated | 2022-06-27 | 2026-04-07 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| 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 | 9 stars, 13k npm/wk | none |
| Agent reviews | 3.3/5 (4) | none |

## How the scores have moved

### Creatomate

- +1.8 on 4 November 2026: new evidence
- -0.2 on 28 October 2026: new evidence
- +0.3 on 27 October 2026: checklist

### Pixelixe

No score change since it was listed.

## Verdicts

**Creatomate.** A hosted MCP server with eight tools and OAuth with PKCE sits beside a small REST API whose errors carry a hint and a documentation link, a documented rate limit with `Retry-After`, and a free `dry_run`. No status page, changelog, OpenAPI file or security contact was found, and the terms and privacy policy date from June 2022.

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

## Before you call either

### Creatomate

1. Send `"dry_run": true` to `POST /v2/renders` before a paid render. It returns `valid`, `errors`, `warnings` and the effective source
2. Read `warnings` on every render response. A modification keyed to an unknown element or property name is ignored without an error
3. Keep under 30 requests per 10 seconds across the whole account, and wait for `Retry-After` on a 429
4. Download each file when the webhook fires. Renders, their URLs and their status records are deleted after 30 days
5. Use `render_scale` 0.5 for draft videos, about a quarter of the credits, and remember MCP `create_render` spends credits without a confirmation step from the server

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

## Questions

### Which is better for AI agents, Creatomate or Pixelixe?

Creatomate scores 49.6 (D) on agent readiness against Pixelixe's 37.3 (F), and leads in 6 of 7 scored categories. Pixelixe leads on schema & documentation.

### Do Creatomate and Pixelixe need an API key?

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

### Can an agent call Creatomate and Pixelixe without installing anything?

Yes. Creatomate has a hosted endpoint at https://api.creatomate.com/v2 and Pixelixe at https://studio.pixelixe.com/api.


## For agents

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

## Other comparisons with Creatomate or Pixelixe

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