Head to head · Design rendering · October 2026 research run
Clayzo vs Layerre
Layerre scores 59.2 (C) on agent readiness against Clayzo's 50.9 (D), and leads in 4 of 7 scored categories. Clayzo leads on payments & pricing. 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
- Payments & pricing, 55 against 38
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
Layerre C
Best for Bulk image and PDF variants from Canva designs a team already has.
Ahead on
- Reliability, 42 against 33
- Schema & documentation, 87 against 57
- Maintenance & community, 78 against 58
- Transparency & trust, 63 against 26
Also in its favour
- Runs on your own machine
Watch for
Imports Canva designs only; there is no template editor of its own
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 Layerre +37
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.
Layerre 63
The MCP server is MIT. The service is closed under terms of 13 August 2026 that name a sole proprietorship in Ontario (20 of 30). The privacy policy and DPA of the same date agree. Data is kept while the account is active and deleted from production on account deletion, with limited backups. Design files aren't used to train public AI models. Google Analytics runs on accepted cookies (24 of 30). No deprecation policy or notice period (0). Ten subprocessors listed with purpose and location in both documents, including Supabase, Stripe, Cloudflare, Google, Resend, Canva and Slack (20). 20 + 24 + 0 + 20 = 64.
Schema & documentation Layerre +30
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.
Layerre 87
Public OpenAPI 3.1 at layerre.com/openapi.json with 16 operations, and zod schemas on all 13 MCP tools in the open-source server (25). llms.txt, auth.md and Markdown mirrors of the pricing, FAQ and integration pages (10). Every operation has a description, and tool descriptions note costs such as 'an expensive operation that may take 10-30 seconds', without saying when not to use a tool (15 of 20). Layer properties have minimums, maximums and enums such as text_align, and list calls cap limit at 1,000 (14 of 15). 88 examples in the spec, and 404, 422 and 429 responses documented on most operations (13 of 15). Versioned /v1 paths and dated What's New pages, read from the sitemap since the pages are drawn by script; the API itself is version 0.1.0 (10 of 15). 25 + 10 + 15 + 14 + 13 + 10 = 87.
Maintenance & community Layerre +20
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.
Layerre 78
@layerre/mcp-server 0.1.0 published to npm on 29 October 2026, 8 days before this check (30). MCP server commits from 19 to 24 October, the registry entry of 29 October, and What's New entries dated 21 August and 18 October in the sitemap (20). The repository is a week old with no issues to judge; support by email and in-app chat (5 of 25). com.layerre/layerre is in the official MCP registry under a domain-verified namespace (15). CI runs the vitest suite on push and pull requests to main on Node 22 (8 of 10). 30 + 20 + 5 + 15 + 8 = 78.
Payments & pricing Clayzo +17
Clayzo 55
Read as a free package with a hosted sign-in, since nothing is sold for a user's own sites. No x402, MPP or L402 (0). The price is stated publicly as free for animations on your own sites and apps, while a product built on Clayzo needs a licence by email with no price (20 of 30). Free with a sign-in, no card mentioned anywhere read (30). A person approves the device in a browser before any protected command. After that a CI token can be created from the CLI, a programmatic route after a human sign-in (5 of 30). 0+20+30+5 = 55.
Layerre 38
No x402, MPP or L402 (0). Plan prices are public with render counts, and one import or one variant is one render, so the price a render follows from the plan (about $0.03 on Starter, $0.005 on Pro) without being published per unit (15 of 20). Free plan of 50 renders a month with API access; the pricing page doesn't say whether a card is needed (10 of 20, half as with an unstated card rule). A person signs up and creates the key, or approves OAuth in a browser (0). 0 + 15 + 10 + 0 = 25. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 25 is 38.
Reliability Layerre +9
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.
Layerre 42
Hosted lines, for the REST API and the hosted MCP server. No status page found on the site, in llms.txt or in the docs (0). No readable incident history (5). Rate limits published as 10 requests a second, a 20-request burst and 600 a minute per IP address (15). A 429 carries Retry-After and a retry_after field, and the docs give retry code samples. No idempotency key or safe-retry note for variant creation, which spends renders (12 of 15). No SLA found (0). Neither surface is labelled beta, though both are at version 0.1.0 (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.
Score by category
| Category | Weight | Clayzo | Layerre | Edge |
|---|---|---|---|---|
| Reliability | 16% | 33 | 42 | Layerre +9 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 87 | Layerre +30 |
| Agent ergonomics | 13% | 72 | 69 | Clayzo +3 |
| Security & auth | 14% | 52 | 48 | Clayzo +4 |
| Payments & pricing | 10% | 55 | 38 | Clayzo +17 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 58 | 78 | Layerre +20 |
| Transparency & trust | 7% | 26 | 63 | Layerre +37 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 50.9/100 | C 59.2/100 |
Facts side by side
| Fact | Clayzo | Layerre |
|---|---|---|
| Kind | SDK + MCP | HTTP API |
| Vendor | Clayzo | Layerre |
| Hosted endpoint | https://app.clayzo.com/api/clayzo/mcp | https://api.layerre.com/v1 |
| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | none | MIT for the MCP server. The Layerre API is a closed service under terms last updated 13 August 2026 |
| Tools exposed | none | 13 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | com.layerre/layerre |
| Last release | 2026-11-17 | 2026-10-29 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | couldn't be read | no date given |
| 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 | 119 npm/wk |
How the scores have moved
Clayzo
No score change since it was listed.
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.
Layerre
A public OpenAPI 3.1 contract, published rate limits with Retry-After, and 13 annotated MCP tools that can't delete anything make Layerre straightforward for an agent to call. It works only from Canva designs, is run by a sole proprietor with no status page or SLA, and its API and MCP server are at version 0.1.0.
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
Layerre
- Call
layerre_auth_statusfirst to confirm the connection - Read a template's layer IDs with
layerre_get_templatebefore creating variants - Use the bulk variant endpoint for batches; each variant still costs one render
- On 429 wait for the Retry-After seconds; limits are per IP address
- Expect template import from a Canva link to take 10 to 30 seconds
Questions
Which is better for AI agents, Clayzo or Layerre?
Layerre scores 59.2 (C) on agent readiness against Clayzo's 50.9 (D), and leads in 4 of 7 scored categories. Clayzo leads on payments & pricing.
Can an agent call Clayzo and Layerre without installing anything?
Yes. Clayzo has a hosted endpoint at https://app.clayzo.com/api/clayzo/mcp and Layerre at https://api.layerre.com/v1.
Other comparisons with Clayzo or Layerre
- Adobe Photoshop API vs Layerre
- APITemplate.io vs Clayzo
- APITemplate.io vs Layerre
- Bannerbear API + MCP vs Clayzo
- Bannerbear API + MCP vs Layerre
- Canva REST APIs + MCP vs Clayzo
- Canva REST APIs + MCP vs Layerre
- Clayzo vs Photoroom API
- Contentdrips API and MCP vs Layerre
- Creatomate vs Layerre
- DynaPictures vs Layerre
- Layerre vs Photoroom API
- Layerre vs Pictify
- Layerre vs Pixelixe
- Layerre vs Placid API + MCP
- Layerre vs PostNitro
- Layerre vs Robolly
- Layerre vs Shotstack
- Layerre vs Templated API + MCP
- Abyssale vs Clayzo
- Abyssale vs Layerre
- Adobe Photoshop API vs Clayzo
- Clayzo vs Contentdrips API and MCP
- Clayzo vs Creatomate
- Clayzo vs DynaPictures
- Clayzo vs Osmo CLI
- Clayzo vs Pictify
- Clayzo vs Pixelixe
- Clayzo vs Placid API + MCP
- Clayzo vs PostNitro
- Clayzo vs Robolly
- Clayzo vs Shotstack
- Clayzo vs Templated API + MCP
- Layerre vs Osmo CLI
Machine-readable
- This page as Markdown
/compare/clayzo-vs-layerre.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/clayzo.json·/api/v1/tools/layerre.json - From a terminal
anchor compare clayzo layerre(the CLI) - Over MCP
compare_tools {"a": "clayzo", "b": "layerre"}at/mcp, no key