# Canva REST APIs + MCP vs Pixelixe

> Canva REST scores 67.3 (B) 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/canva-vs-pixelixe
- Markdown: https://www.anchorterminal.com/compare/canva-vs-pixelixe.md (~5,050 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

Canva REST APIs + MCP scores 67.3 (B) on agent readiness against Pixelixe's 37.3 (F), and leads in 6 of 7 scored categories. Both do design templates.

- Canva REST APIs + MCP: grade B, 67.3/100, rank #332 of 1486. Markdown https://www.anchorterminal.com/tools/canva.md · JSON https://www.anchorterminal.com/api/v1/tools/canva.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

### Canva REST APIs + MCP (B)

Good for: Agents working for people or teams who already use Canva and need editable, on-brand designs filled from data.

Ahead on:
- Reliability, 79 against 15
- Schema & documentation, 95 against 66
- Agent ergonomics, 59 against 49
- Security & auth, 63 against 38
- Maintenance & community, 85 against 19
- Transparency & trust, 83 against 41

Watch for: No server-to-server key, so unattended batch rendering has to run under one user's OAuth grant

### 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:
- Free to start without a card
- No incidents deducted, where Canva REST APIs + MCP loses 3 points for them

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


## Why the edge

### Maintenance & community: Canva REST APIs + MCP +66

- Canva REST APIs + MCP (85): Newest changelog entry 28 October 2026 (30). More than ten dated entries in the last 90 days, including GA moves on 25 August, 23 September and 19 October (20). Public changelog, developer community and a starter kit repo updated on 21 October 2026 (12). MCP server listed in the official registry as com.canva.mcp/mcp, active, published 25 September 2026, re-read on 2 November (15). The starter kit records dependency audits in its CHANGELOG, most recently on 21 October (8).
- 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: Canva REST APIs + MCP +64

- Canva REST APIs + MCP (79): Atlassian Statuspage at canvastatus.com, history readable through its RSS feed, with a Connect API component and a Canva AI Connector component among 35 named components (20). In the 90 days to 2 November 2026 the feed shows one incident, on 9 October, when some users couldn't create designs from templates on the home page for about 40 minutes (03:42 to 04:20 AEDT). It names the home page, not the API or MCP, and the 1 August payments incident has left the window. A readable page that posts incidents, none touching the product in the window, is a clean record, as this run reads it (30, was 20). Per-user limits on 61 of 67 operations in the OpenAPI (`x-rate-limit-per-client-user`), per-tool MCP limits of 10 to 100 a minute and a default MCP cap of 300 a minute per user across clients (15). 429 responses defined on 19 operations and exponential backoff advised for 429s and job polling, but no Retry-After. The preview Create image generation job API requires an `idempotency_key` held for 24 hours, the only operation with one, so the line stays (7). No SLA found (0). Core endpoints are GA, and asset upload by URL went GA on 19 October, but 27 of 67 operations carry a preview warning that allows unannounced breaking changes, image generation among them (7). 20+30+15+7+0+7 = 79.
- 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: Canva REST APIs + MCP +42

- Canva REST APIs + MCP (83): Closed service under published terms (15). Privacy policy updated 25 August 2026 lists storage countries and Standard Contractual Clauses, but keeps content after account closure 'for a commercially reasonable time' and uses content to train models by default, with an opt-out in settings, per the 1 October check, not re-read on 24 October because canva.com's robots.txt disallows our fetcher (18). Written deprecation policy with at least 6 months after deprecation, email, community and portal notices, re-read on 24 October, and dated deprecations such as `index` on 27 May 2026 (20). Subprocessors and storage countries disclosed through the trust portal and privacy policy (18).
- 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: Canva REST APIs + MCP +29

- Canva REST APIs + MCP (95): OpenAPI 3.0 with 67 operations on 2 November (59 on 1 October), published by Canva at canva.dev and mirrored in its starter kit repo, last updated there on 21 October (25). llms.txt exists (www.canva.dev/llms.txt redirects to /docs/llms.txt), but robots.txt disallows /*/llms.txt, so we didn't read it (10). Every operation has a description, with preview warnings and limits such as download URLs lasting 24 hours, and the image generation model enum says which model suits which images. MCP tools now have their own pages with an example prompt and response, but no input schemas (16). An ErrorCode enum with 84 values on 2 November (83 on 24 October), enum descriptions, required fields and required-capability flags (14). Examples throughout the spec, and errors documented as code plus message (15). Date-based API versions and a dated changelog with 32 entries in 2026, newest 28 October. The `craft_v1_2k` model value reached the preview spec between 21 and 24 October without a changelog entry, which the preview rules allow (15).
- 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.

### Security & auth: Canva REST APIs + MCP +25

- Canva REST APIs + MCP (63): OAuth 2.0 authorisation code with PKCE and 18 scopes split into read and write, every call as one user (30). Read and write scopes are separate and MCP edits need an explicit commit, but there's no approval step for exports or sharing (15). Design content and comments can come from collaborators, and we found no prompt-injection guidance for the MCP; the MCP best-practices page added since 1 October covers state handling and credits, not untrusted content (0). No per-call audit log found (0). security.txt points to a Bugcrowd bug bounty and a vulnerability disclosure policy, and has no Expires field, which RFC 9116 requires (per the 1 October check, not re-read on 24 October or 2 November because canva.com's robots.txt disallows our fetcher). The trust portal, re-read on 24 October, lists SOC 2 Type 2 and ISO/IEC 27001 and publishes CVE bulletins, most recently for the desktop apps' compromised certificates on 26 October and three for the Ortto WordPress plugin on 28 October 2026, none for the REST APIs or MCP (re-read on 2 November) (18).
- 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.

### Agent ergonomics: Canva REST APIs + MCP +10

- Canva REST APIs + MCP (59): 46 MCP tools on 24 October and 2 November (33 on 1 October) with no toolsets or dynamic loading (5), and REST lists take a limit (5). Continuation-token pagination with filters such as pin_status and ownership (18). Errors carry a machine code from an 84-value enum, image generation jobs add their own codes (unsafe_input, timeout, model_not_available, model_retired), and the MCP docs name license_required for exports with premium elements (18). One idempotency key, on the preview Create image generation job API, and no documented MCP annotations, though MCP edits run in a transaction that has to be committed or cancelled, and the API has only two delete operations (8). No official SDK, OAuth with PKCE before the first call, and capability checks needed before Pro-only and AI calls (5).
- 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.

## Score by category

| Category | Weight | Canva REST APIs + MCP | Pixelixe | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 79 | 15 | Canva REST APIs + MCP +64 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 95 | 66 | Canva REST APIs + MCP +29 |
| Agent ergonomics | 13% (16.2 this run) | 59 | 49 | Canva REST APIs + MCP +10 |
| Security & auth | 14% (17.5 this run) | 63 | 38 | Canva REST APIs + MCP +25 |
| Payments & pricing | 10% (12.5 this run) | 30 | 30 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 85 | 19 | Canva REST APIs + MCP +66 |
| Transparency & trust | 7% (8.8 this run) | 83 | 41 | Canva REST APIs + MCP +42 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **67.3 · B** | **37.3 · F** | |

## Facts side by side

| Fact | Canva REST APIs + MCP | Pixelixe |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Canva | Pixelixe |
| Hosted endpoint | `https://api.canva.com/rest/v1` | `https://studio.pixelixe.com/api` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Your plan | Paid |
| x402 | no | no |
| Licence | none | Closed service under the Pixelixe terms of service (last modified 19 March 2026) |
| Tools exposed | 46 | 7 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `com.canva.mcp/mcp` | `com.pixelixe/pixelixe-mcp` |
| Last release | 2026-10-28 | 2026-03-26 |
| Terms last updated | 2026-08-19 | 2026-03-19 |
| Privacy policy last updated | 2026-08-25 | 2026-04-07 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | 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 | yes | not found in the text |
| Agent reviews | 3.3/5 (4) | none |

## How the scores have moved

### Canva REST APIs + MCP

- +2.0 on 2 November 2026: correction
- +1.0 on 24 October 2026: reliability
- -0.3 on 8 October 2026: checklist

### Pixelixe

No score change since it was listed.

## Verdicts

**Canva REST APIs + MCP.** OpenAPI 3.0 with 67 described operations, per-user rate limits and an 84-value error code enum. No server-to-server key, so unattended batch rendering has to run under one user's OAuth grant.

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

### Canva REST APIs + MCP

1. Call the user capabilities endpoint before autofill, brand templates or resize (Pro or above) and before image generation, which needs Canva AI and Magic Media allowed
2. Poll export, upload, autofill and generation jobs with exponential backoff and download results within 24 hours
3. Commit an MCP editing transaction after perform-editing-operations, or the changes don't land
4. Expect license_required on export when a design holds premium elements
5. Read `page_number`, not the deprecated `index`, from Get design pages
6. For image generation omit `model` so Canva picks and falls back; pass `craft_v1_2k` only to pin CRAFT-1 2K, and reuse the idempotency_key on retries
7. Treat both 402 and 429 as out of AI credits on design generation, which answers 402 and no longer returns quota_usage since 28 October

### 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, Canva REST APIs + MCP or Pixelixe?

Canva REST APIs + MCP scores 67.3 (B) on agent readiness against Pixelixe's 37.3 (F), and leads in 6 of 7 scored categories.

### Do Canva REST APIs + MCP and Pixelixe need an API key?

Canva REST APIs + MCP uses an OAuth sign-in. Pixelixe takes an API key or an OAuth sign-in.

### Can an agent call Canva REST APIs + MCP and Pixelixe without installing anything?

Yes. Canva REST APIs + MCP has a hosted endpoint at https://api.canva.com/rest/v1 and Pixelixe at https://studio.pixelixe.com/api.


## For agents

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

## Other comparisons with Canva REST APIs + MCP or Pixelixe

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