Head to head · Design rendering · October 2026 research run
Clayzo vs DynaPictures
Clayzo scores 50.9 (D) on agent readiness against DynaPictures's 45.1 (E), and leads in 4 of 7 scored categories. DynaPictures leads on reliability, schema & documentation and transparency & trust. 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
- Agent ergonomics, 72 against 45
- Security & auth, 52 against 26
- Payments & pricing, 55 against 45
- Maintenance & community, 58 against 4
Watch for
preview, render-frame, review, package and export need a Clayzo sign-in approved in a browser
Best for Personalised images and PDFs per record, image URLs in emails and pages, and email countdown timers, for marketing teams in the EU.
Ahead on
- Reliability, 42 against 33
- Schema & documentation, 82 against 57
- Transparency & trust, 63 against 26
Watch for
One API key per user with full account access and no scopes; a new key needs an email to support
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.
Maintenance & community Clayzo +54
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.
DynaPictures 4
No changelog, release notes or dated API change was found, and the MCP server card gives version 1.0.0 with no date (0). No dated changes since 8 August (0). Support by email and contact form, not tested (4 of 15). Not in the official MCP registry and no API SDKs (0). No public package or repository (0). 0 + 0 + 4 + 0 + 0 = 4.
Transparency & trust DynaPictures +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.
DynaPictures 63
Closed service under terms (revision 2/2026) from DynaPictures GmbH in Freiburg, for business customers (15). The privacy policy names the controller, keeps generated images as long as needed or until deleted, gives plan image retention (3 months on Lite), and says the named AI providers don't train on API inputs under their API terms; other periods follow bookkeeping law (20 of 30). The OpenAPI file commits to six months' notice before removing an endpoint or field, with Deprecation and Sunset headers (16 of 20). AI sub-processors named with addresses (OpenAI, Google, Black Forest Labs, Replicate) and FastSpring for payments, while hosting providers aren't named (12 of 20). 15 + 20 + 16 + 12 = 63.
Agent ergonomics Clayzo +27
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.
DynaPictures 45
The MCP tool definitions weren't read (listing them needs a session), and llms.txt describes groups that include layer-by-layer design authoring, so the count is unknown. REST responses are small objects with image URLs (12 of 25). Template and generated-image listings, with no field selection documented (10 of 20). Errors are JSON with a message and documented statuses, without codes (12 of 20). Requests aren't idempotent, by the vendor's own note, though identical image URLs are served from cache without a credit (6 of 20). An Editor SDK for embedding the editor, and no API client SDKs (5 of 15). 12 + 10 + 12 + 6 + 5 = 45.
Security & auth Clayzo +26
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.
DynaPictures 26
One API key per user with the user's full access, not limited to workspaces or actions; a new key is requested by email to support, with no rotation in the account (10 of 30). No read-only mode, and the MCP server can author and change designs (3 of 20). Tools return the account's own templates and renders; image layers accept outside URLs (10 of 15). A list of generated images, with no audit log documented (3 of 15). No security.txt, disclosure policy, bug bounty or certification found (0). 10 + 3 + 10 + 3 + 0 = 26.
Schema & documentation DynaPictures +25
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.
DynaPictures 82
OpenAPI 3.1 at dynapictures.com/openapi.json with 20 paths (25). llms.txt, auth.md and an agent skill in Markdown (10). llms.txt says when to use the product and when it's a poor fit, and the skill gives call order for each job (17 of 20). Enums for formats and options, with layer overrides keyed by layer name (12 of 15). Request examples throughout and a status table in the skill, but the API reference's Errors section is unedited Slate template text about kittens (9 of 15). No URL version, additive changes, removals announced six months ahead with Deprecation and Sunset headers, and no changelog (9 of 15). 25 + 10 + 17 + 12 + 9 + 9 = 82.
Payments & pricing Clayzo +10
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.
DynaPictures 45
No x402, MPP or L402 (0). Image allowances per plan and AI credit packs ($20 for 1,000 credits) are public, but plan prices are filled in by the FastSpring script and weren't readable (10 of 20). Free plan and a 14-day trial with 30 API credits, no card (20). auth.md says a person has to copy the key; there is no OAuth or programmatic key (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Score by category
| Category | Weight | Clayzo | DynaPictures | Edge |
|---|---|---|---|---|
| Reliability | 16% | 33 | 42 | DynaPictures +9 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 82 | DynaPictures +25 |
| Agent ergonomics | 13% | 72 | 45 | Clayzo +27 |
| Security & auth | 14% | 52 | 26 | Clayzo +26 |
| Payments & pricing | 10% | 55 | 45 | Clayzo +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 58 | 4 | Clayzo +54 |
| Transparency & trust | 7% | 26 | 63 | DynaPictures +37 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 50.9/100 | E 45.1/100 |
Facts side by side
| Fact | Clayzo | DynaPictures |
|---|---|---|
| Kind | SDK + MCP | HTTP API |
| Vendor | Clayzo | DynaPictures GmbH |
| Hosted endpoint | https://app.clayzo.com/api/clayzo/mcp | https://api.dynapictures.com |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | none | Closed service under the DynaPictures terms of use (revision 2/2026) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-17 | none |
| 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 |
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.
DynaPictures
An OpenAPI 3.1 file, an agent skill and a six-month removal notice with Sunset headers make DynaPictures' template rendering easy to plan around, with a free plan and no-card trial. The single API key opens the whole account, requests aren't idempotent, and no changelog, status page or dated release was found.
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
DynaPictures
- Use
GET /templatesto find a template UID and its layer names before generating - Check whether an image exists before retrying a timed-out
POST /designs/{UID}; retries can be charged - Treat 403 as a spent quota or expired trial and stop; wait for
Retry-Afteronly on 503 - Poll
GET /ai/generate/{jobUid}about every 2 seconds and download the result, since the URL may expire - Keep the API key out of image URLs; use signed or public links for embedding
Questions
Which is better for AI agents, Clayzo or DynaPictures?
Clayzo scores 50.9 (D) on agent readiness against DynaPictures's 45.1 (E), and leads in 4 of 7 scored categories. DynaPictures leads on reliability, schema & documentation and transparency & trust.
Can an agent call Clayzo and DynaPictures without installing anything?
Yes. Clayzo has a hosted endpoint at https://app.clayzo.com/api/clayzo/mcp and DynaPictures at https://api.dynapictures.com.
Other comparisons with Clayzo or DynaPictures
- Adobe Photoshop API vs DynaPictures
- APITemplate.io vs Clayzo
- APITemplate.io vs DynaPictures
- Bannerbear API + MCP vs Clayzo
- Bannerbear API + MCP vs DynaPictures
- Canva REST APIs + MCP vs Clayzo
- Canva REST APIs + MCP vs DynaPictures
- Clayzo vs Photoroom API
- Contentdrips API and MCP vs DynaPictures
- Creatomate vs DynaPictures
- DynaPictures vs Layerre
- DynaPictures vs Photoroom API
- DynaPictures vs Pictify
- DynaPictures vs Pixelixe
- DynaPictures vs Placid API + MCP
- DynaPictures vs PostNitro
- DynaPictures vs Robolly
- DynaPictures vs Shotstack
- DynaPictures vs Templated API + MCP
- Abyssale vs Clayzo
- Abyssale vs DynaPictures
- Adobe Photoshop API vs Clayzo
- Clayzo vs Contentdrips API and MCP
- Clayzo vs Creatomate
- 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
- Clayzo vs Templated API + MCP
- DynaPictures vs Osmo CLI
Machine-readable
- This page as Markdown
/compare/clayzo-vs-dynapictures.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/clayzo.json·/api/v1/tools/dynapictures.json - From a terminal
anchor compare clayzo dynapictures(the CLI) - Over MCP
compare_tools {"a": "clayzo", "b": "dynapictures"}at/mcp, no key