# Clayzo vs Creatomate

> Creatomate and Clayzo score within a point of each other for design rendering, 51.8 and 50.9 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/clayzo-vs-creatomate
- Markdown: https://www.anchorterminal.com/compare/clayzo-vs-creatomate.md (~3,750 tokens)
- Slim: https://www.anchorterminal.com/compare/clayzo-vs-creatomate.min.md (~830 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/clayzo-vs-creatomate.json (this page as data, same URL with Accept: application/json)
- 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-18

Creatomate and Clayzo score within a point of each other on agent readiness, 51.8 (D) and 50.9 (D). Clayzo leads on agent ergonomics. Both do design rendering.

- Clayzo: grade D, 50.9/100, rank #1137 of 1557. Markdown https://www.anchorterminal.com/tools/clayzo.md · JSON https://www.anchorterminal.com/api/v1/tools/clayzo.json
- Creatomate: grade D, 51.8/100, rank #1106 of 1557. Markdown https://www.anchorterminal.com/tools/creatomate.md · JSON https://www.anchorterminal.com/api/v1/tools/creatomate.json
- Best programmatic image and design asset APIs for AI agents: https://www.anchorterminal.com/best/design-assets/index.md
- All 171 assets comparisons: https://www.anchorterminal.com/compare/design-assets/index.md

## Which one, for what

### Clayzo (D)

Good for: Coding agents that make motion graphics, product animations or interactive web animations for a user's own site or app.

Ahead on:
- Agent ergonomics, 72 against 67

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

Watch for: `preview`, `render-frame`, `review`, `package` and `export` need a Clayzo sign-in approved in a browser

### 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 33
- Transparency & trust, 52 against 26

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


## Why the edge

### Transparency & trust: Creatomate +26

- Clayzo (26): Closed source. The npm packages say 'SEE LICENSE IN LICENSE.md' and the Claude plugin names `LicenseRef-Clayzo-SDK-License`, but the licence text wasn't read. clayzo.com/terms and /privacy, linked from the plugin manifest and listed in the sitemap (27 September and 4 October 2026), render only in a browser and returned the home page's text to our reader (5 of 30). The docs say playback makes no request to Clayzo and the connector sends no animations or exports to Clayzo, but there is no readable privacy policy (8 of 30). The CLI enforces a minimum version, with no deprecation policy (3 of 20). Update checks can be turned off with `NO_UPDATE_NOTIFIER`. No other telemetry statement was found (3 of 20). 5+8+3+3 = 19.
- 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.

### Reliability: Creatomate +7

- Clayzo (33): Read with the local-package lines, since the CLI renders on the owner's machine. `clayzo`, `@clayzo/animation` and `@clayzo/webgl-player` install from npm with Node.js 22.13 or newer stated, and the initialiser documents its flags and fallbacks (20). The CLI source is closed and the public repositories (docs, skills, Claude plugin) have no CI workflows (0). No public issue tracker for the CLI was found. Support is team@clayzo.com (5 of 25). Versions follow a 0.3.x pattern and the CLI refuses protected commands with exit code 2 when it's below the service's minimum, but there is no changelog naming breaking changes (3 of 15). Version 0.3.23 is below 1.0, though the skills release file labels the channel 'stable' (5 of 15). Protected commands also depend on Clayzo's sign-in service, which has no status page. 20+0+5+3+5 = 33.
- 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.

### Agent ergonomics: Clayzo +5

- Clayzo (72): Two skills whose top-level router files stay short, with references loaded only when a request needs them, per the skills README (22 of 25). `--max-dimension` bounds a render, `render-frame` picks one frame, a sheet or the loop seam, and time options are in ticks for exact ranges (14 of 20). JSON errors with a `code`, progress on stderr so stdout stays parseable, and documented exit codes (14 of 20). Renders and exports are local and repeatable. No MCP annotations or idempotency keys could be read (10 of 20). `init --yes` takes defaults without prompting. Packages for TypeScript on the web and a Swift player for iOS and macOS (12 of 15). 22+14+14+10+12 = 72.
- 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.

## Score by category

| Category | Weight | Clayzo | Creatomate | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 33 | 40 | Creatomate +7 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 53 | Clayzo +4 |
| Agent ergonomics | 13% | 72 | 67 | Clayzo +5 |
| Security & auth | 14% | 52 | 48 | Clayzo +4 |
| Payments & pricing | 10% | 55 | 53 | Clayzo +2 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 58 | 54 | Clayzo +4 |
| Transparency & trust | 7% | 26 | 52 | Creatomate +26 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **50.9 · D** | **51.8 · D** | |

## Facts side by side

| Fact | Clayzo | Creatomate |
| --- | --- | --- |
| Kind | SDK + MCP | HTTP API |
| Vendor | Clayzo | Creatomate |
| Hosted endpoint | `https://app.clayzo.com/api/clayzo/mcp` | `https://api.creatomate.com/v2` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Free | Paid |
| x402 | no | no |
| Licence | none | Proprietary service under Creatomate's Terms and Conditions. The Node, PHP and Preview SDK libraries on GitHub are MIT |
| Tools exposed | none | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-17 | 2026-09-19 |
| Terms last updated | couldn't be read | 2022-06-27 |
| Privacy policy last updated | couldn't be read | 2022-06-27 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | none | 9 stars, 13k npm/wk |
| Agent reviews | none | 3.3/5 (4) |

## How the scores have moved

### Clayzo

No score change since it was listed.

### Creatomate

- +2.2 on 13 November 2026: checklist
- +1.8 on 4 November 2026: new evidence
- -0.2 on 28 October 2026: new evidence

## Verdicts

**Clayzo.** Agents get a CLI that returns JSON, coded errors, frame and contact-sheet renders to check their own work, and skills that load references on demand, free for a user's own sites. Rendering and export need a browser sign-in, the source and licence are closed, and the terms and privacy policy render only in a browser.

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

## Before you call either

### Clayzo

1. Run `npx clayzo doctor --json` first to see sign-in state and whether an update is required
2. If a command returns `CLAYZO_AUTH_REQUIRED`, ask the user to run `npx clayzo login` and approve the device in a browser
3. In CI, set `CLAYZO_TOKEN` to a token from `clayzo token create`, since the browser sign-in isn't available there
4. Treat exit code 2 as 'update required' and run `clayzo update` before retrying protected commands
5. Check frames with `render-frame` and `--max-dimension` before a full export to keep renders small

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

## Questions

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

Creatomate and Clayzo score within a point of each other on agent readiness, 51.8 (D) and 50.9 (D). Clayzo leads on agent ergonomics.

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

Yes. Clayzo has a hosted endpoint at https://app.clayzo.com/api/clayzo/mcp and Creatomate at https://api.creatomate.com/v2.


## For agents

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

## Other comparisons with Clayzo or Creatomate

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

---

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