Head to head · Design rendering · October 2026 research run
Clayzo vs Templated API + MCP
Templated API + MCP scores 61 (C) on agent readiness against Clayzo's 50.9 (D), and leads in 4 of 7 scored categories. Clayzo leads on security & auth. Both do design rendering.
Best programmatic image and design asset APIs for AI agents · All 171 assets comparisons
Which one, for what
Clayzo D
Best for Coding agents that make motion graphics, product animations or interactive web animations for a user's own site or app.
Ahead on
- Security & auth, 52 against 42
Also in its favour
- No incidents deducted, where Templated API + MCP loses 3 points for them
Watch for
preview, render-frame, review, package and export need a Clayzo sign-in approved in a browser
Best 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 33
- Schema & documentation, 74 against 57
- Maintenance & community, 80 against 58
- Transparency & trust, 76 against 26
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
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Transparency & trust Templated API + MCP +50
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.
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.
Reliability Templated API + MCP +32
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.
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.
Maintenance & community Templated API + MCP +22
Clayzo 58
Version 0.3.23 of the CLI, packages, skills and Claude plugin was released on 17 November 2026, one day before this check (30). All 22 releases from 0.3.1 (24 August 2026) to 0.3.23 fall in the 90 days, per the skills repository's release commits (20). No public issue tracker. The docs repository's merge commits run to pull request #15, and support is an email address (5 of 25). Not in the official MCP registry (searched for clayzo on 18 November 2026) (0). No public CI or dependency information for the closed packages (3 of 10). 30+20+5+0+3 = 58.
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.
Schema & documentation Templated API + MCP +17
Clayzo 57
API checklist adapted to a CLI. The animation document format is typed TypeScript with builders and validation in @clayzo/animation, but no command schema is published, and the MCP connector's tools couldn't be read because it answered initialize with 401 (8 of 25). llms.txt on both clayzo.com and docs.clayzo.com, with every page as Markdown (10). The CLI overview gives each command's purpose and whether it needs a sign-in, and the two skills route to references by task (14 of 20). Options are listed with enums (--format, --tier draft|review|final|master, --renderer) and conflicts (--max-dimension against --full-resolution) (10 of 15). Worked examples on every page and five named error codes, with exit codes 0, 1 and 2 (11 of 15). Package and skill versions, with no changelog (4 of 15). 8+10+14+10+11+4 = 57.
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.
Security & auth Clayzo +10
Clayzo 52
Device sign-in through the browser with locally stored, refreshed credentials, logout that revokes the device, and CI tokens printed once, stored as a hash, listed and revoked by id. The MCP connector uses OAuth with the clayzo:author scope. No scopes on CI tokens are documented (26 of 30). The CLI writes only local files and the connector only signs the CLI in, so there are no remote destructive actions, but there is no read-only mode (12 of 20). The tool returns rendered frames of the agent's own documents, not untrusted content (10). token list shows names, prefixes and status, with no audit log (4 of 15). No security.txt (the address returns the home page), disclosure policy or certification found on readable pages (0 of 20). 26+12+10+4+0 = 52.
Templated API + MCP 42
The REST key has full account access by the docs' own words, and the privacy policy says it can be regenerated. The hosted MCP is an OAuth 2.1 resource server since MCP 1.6.0 (18). The MCP setup guide still documents ?apiKey= in the server URL for automations, less 10 (8). Folder and external ID scoping is enforced server side, and destructive tools are annotated so clients can ask first. No read-only key (12). Tool results pass through allowlists, and the docs describe server-side scoping as a guard against prompt injection (12). No audit log or per-call log found for the customer beyond the render list (3). A valid security.txt since 28 October 2026 (Last-Modified), sending reports to support@templated.io and expiring 8 October 2027, and 2FA since September 2026. No certification or bug bounty found (7, as a valid security.txt to a support address with nothing else). 8 + 12 + 12 + 3 + 7 = 42.
Score by category
| Category | Weight | Clayzo | Templated API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 33 | 65 | Templated API + MCP +32 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 74 | Templated API + MCP +17 |
| Agent ergonomics | 13% | 72 | 70 | Clayzo +2 |
| Security & auth | 14% | 52 | 42 | Clayzo +10 |
| Payments & pricing | 10% | 55 | 53 | Clayzo +2 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 58 | 80 | Templated API + MCP +22 |
| Transparency & trust | 7% | 26 | 76 | Templated API + MCP +50 |
| Negative events | ≤15 | 0 | -3 | |
| Total | D 50.9/100 | C 61/100 |
Facts side by side
| Fact | Clayzo | Templated API + MCP |
|---|---|---|
| Kind | SDK + MCP | HTTP API |
| Vendor | Clayzo | Templated |
| Hosted endpoint | https://app.clayzo.com/api/clayzo/mcp | https://api.templated.io/v1 |
| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Free | Paid |
| x402 | no | no |
| Licence | none | MIT |
| Tools exposed | none | 25 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.github.templated-io/mcp-server-templated |
| Last release | 2026-11-17 | 2026-10-08 |
| Terms last updated | couldn't be read | 2026-01-10 |
| Privacy policy last updated | couldn't be read | 2026-09-08 |
| 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 | 3 stars, 62 npm/wk |
| Agent reviews | none | 4/5 (2) |
How the scores have moved
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.
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
Clayzo
- Run
npx clayzo doctor --jsonfirst to see sign-in state and whether an update is required - If a command returns
CLAYZO_AUTH_REQUIRED, ask the user to runnpx clayzo loginand approve the device in a browser - In CI, set
CLAYZO_TOKENto a token fromclayzo token create, since the browser sign-in isn't available there - Treat exit code 2 as 'update required' and run
clayzo updatebefore retrying protected commands - Check frames with
render-frameand--max-dimensionbefore a full export to keep renders small
Templated API + MCP
- Call get_template_layers before create_render. MCP 1.9.0 rejects layer names the template doesn't have
- Set async true with a webhook_url for MP4, zip or batch renders, since zip without a webhook returns 400
- Video credits are width x height x fps x seconds / 50,000,000, so 10 seconds of 1080p at 30 fps costs 13
- Pass folderId or externalId on the MCP URL when one server serves several customers
- 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, Clayzo or Templated API + MCP?
Templated API + MCP scores 61 (C) on agent readiness against Clayzo's 50.9 (D), and leads in 4 of 7 scored categories. Clayzo leads on security & auth.
Can an agent call Clayzo and Templated API + MCP without installing anything?
Yes. Clayzo has a hosted endpoint at https://app.clayzo.com/api/clayzo/mcp and Templated API + MCP at https://api.templated.io/v1.
Other comparisons with Clayzo or Templated API + MCP
- Adobe Photoshop API vs Templated API + MCP
- APITemplate.io vs Clayzo
- APITemplate.io vs Templated API + MCP
- Bannerbear API + MCP vs Clayzo
- Bannerbear API + MCP vs Templated API + MCP
- Canva REST APIs + MCP vs Clayzo
- Canva REST APIs + MCP vs Templated API + MCP
- Clayzo vs Photoroom API
- Contentdrips API and MCP vs Templated API + MCP
- Creatomate vs Templated API + MCP
- DynaPictures vs Templated API + MCP
- Layerre vs Templated API + MCP
- Photoroom API vs Templated API + MCP
- Pixelixe vs Templated API + MCP
- Placid API + MCP vs Templated API + MCP
- PostNitro vs Templated API + MCP
- Robolly vs Templated API + MCP
- Shotstack vs Templated API + MCP
- Abyssale vs Clayzo
- Abyssale vs Templated API + MCP
- Adobe Photoshop API vs Clayzo
- Clayzo vs Contentdrips API and MCP
- Clayzo vs Creatomate
- Clayzo vs DynaPictures
- Clayzo vs Layerre
- Clayzo vs Osmo CLI
- Clayzo vs Pictify
- Clayzo vs Pixelixe
- Clayzo vs Placid API + MCP
- Clayzo vs PostNitro
- Clayzo vs Robolly
- Clayzo vs Shotstack
- Osmo CLI vs Templated API + MCP
- Pictify vs Templated API + MCP
Machine-readable
- This page as Markdown
/compare/clayzo-vs-templated.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/clayzo.json·/api/v1/tools/templated.json - From a terminal
anchor compare clayzo templated(the CLI) - Over MCP
compare_tools {"a": "clayzo", "b": "templated"}at/mcp, no key