Head to head · Design rendering · October 2026 research run
Clayzo vs Placid API + MCP
Clayzo scores 50.9 (D) on agent readiness against Placid API + MCP's 44.9 (E), and leads in 5 of 7 scored categories. Placid API + MCP leads on reliability 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
- Schema & documentation, 57 against 37
- Agent ergonomics, 72 against 40
- Security & auth, 52 against 29
- Maintenance & community, 58 against 7
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
Best for Small teams and no-code builders who want template renders to image, PDF and video at a low monthly price, and agents that should be fenced to a few templates.
Ahead on
- Reliability, 75 against 33
- Transparency & trust, 58 against 26
Watch for
No OpenAPI, no llms.txt, and the MCP tool list isn't published
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 +51
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.
Placid API + MCP 7
We found no dated release or API change. /changelog on placid.app returns 404, the Headway changelog Placid links is barred by its robots.txt (struck), the docs carry no dates and the sitemap's lastmod values are one build time (0). No three dated entries in the last 90 days (0). Support by email named in the error docs; the changelog part of the 1 October partial is struck and the partial is held on the support route, pending review (4). Official PHP and Laravel libraries were last tagged v1.0.1 on 2022-07-20 and still call placid.app/api/rest (3). Placid's own verified n8n community node (n8n-nodes-placid) has a version bump to 0.1.7 on 13 October 2026 in its repository, untagged and with no changelog, and npm couldn't be read, so it isn't counted as a release; no CI on any of the three repositories (0). 0+0+4+3+0 = 7.
Reliability Placid API + MCP +42
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.
Placid API + MCP 75
Hyperping status page at status.placid.app with separate Placid App and Placid API components and 90-day bars (20). No incident is posted, and on 5 November 2026 the page gives the API 100.000 per cent and the App 99.999 per cent for August to November; a page that has never posted an incident takes this run's 20, the same value the 1 October reading gave for 99.963 per cent with no write-up (20). 60 requests a minute and 10 simultaneous create_now requests, documented (15). X-RateLimit-Limit, -Remaining and -Reset headers and exponential backoff advice on 429, but no idempotency key or safe-retry note for renders, which are writes (10). No SLA on the pricing page, in the docs or in the terms (25 November 2024), which promise notice only for a disruption over 24 hours (0). REST API 2.0 is GA (10). 20+20+15+10+0+10 = 75.
Agent ergonomics Clayzo +32
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.
Placid API + MCP 40
Image, PDF and video objects are small and the MCP can be limited to chosen templates and creative types (15). List all templates returns 20 items a page with cursored prev and next links and filters by collection_id, title_filter and tag (nested tags included) with order_by sorting, but has no page-size or field selection, so the line is partly met and keeps its earlier partial, pending review (5). Six HTTP status codes without an error body format, plus documented render error codes with recovery guidance and the layer that failed; the HTTP errors still have no body, so the line is partly met and keeps its earlier partial, pending review (10). No idempotency key, no MCP tool annotations we could see, and DELETE removes an image for good. Polling the polling_url is safe (3). Only template_uuid is required, but the official libraries are PHP and Laravel only, both last tagged v1.0.1 on 2022-07-20 (7). 15+5+10+3+7 = 40.
Transparency & trust Placid API + MCP +32
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.
Placid API + MCP 58
Closed service under published terms naming Nifty Software GmbH, last updated 25 November 2024 (15). Privacy policy updated 18 November 2024, data processing agreements 'whenever necessary', and raw request data kept 'for a limited amount of time' with no period stated (12). No deprecation policy; the 1 October evidence (the old changelog) is struck, and the partial is held on the error docs marking the image reply's errors field 'Deprecated, will be removed' with no date (3). Subprocessor categories only, with 'We don't publish further details of our data processors', and no hosting location (3). 15+12+3+3 = 33.
Security & auth Clayzo +23
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.
Placid API + MCP 29
One bearer token per project, no scopes, and the docs say nothing on revoking or rotating it (15). The MCP setup guide documents ?api_token= in the server URL for clients that can't set headers, less 10 (5). MCP settings restrict which templates and which output types (image, PDF, video, docs only) the server can use (14). Returns renders from your own templates (10). The 1 October award for a dashboard activity log rested only on the Headway changelog, whose robots.txt now bars us, so it is struck, and no per-call log is documented on placid.app (0). No security.txt (404), no certification in the privacy policy and no disclosure policy found (0). 5+14+10+0+0 = 29.
Schema & documentation Clayzo +20
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.
Placid API + MCP 37
No OpenAPI or other machine-readable contract, and the MCP tool definitions aren't published (0). /llms.txt returns 404 (0). Endpoint pages state purpose and warn that create_now may fail under high load (12). template_uuid is the one required field and status is an enum, but layers and modifications are open objects keyed by layer name (8). Request and response examples per endpoint; the error page lists six HTTP codes (400, 401, 404, 422, 429, 500) with no body format, and since the 1 October check a render-error section with ten stable error_code values, an error_message and per-layer error_details, each code saying who can fix it (12). Docs are versioned 2.0 with a 1.0 overview kept; the changelog Placid links is on headwayapp.co, whose robots.txt now bars all crawlers it doesn't name, so the 1 October reading of it is struck and the partial is held on the docs versioning alone, pending review (5). 0+0+12+8+12+5 = 37.
Score by category
| Category | Weight | Clayzo | Placid API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 33 | 75 | Placid API + MCP +42 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 37 | Clayzo +20 |
| Agent ergonomics | 13% | 72 | 40 | Clayzo +32 |
| Security & auth | 14% | 52 | 29 | Clayzo +23 |
| Payments & pricing | 10% | 55 | 53 | Clayzo +2 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 58 | 7 | Clayzo +51 |
| Transparency & trust | 7% | 26 | 58 | Placid API + MCP +32 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 50.9/100 | E 44.9/100 |
Facts side by side
| Fact | Clayzo | Placid API + MCP |
|---|---|---|
| Kind | SDK + MCP | HTTP API |
| Vendor | Clayzo | Placid |
| Hosted endpoint | https://app.clayzo.com/api/clayzo/mcp | https://api.placid.app/api/rest |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Free | Paid |
| x402 | no | no |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-11-17 | none |
| Terms last updated | couldn't be read | 2024-11-25 |
| Privacy policy last updated | couldn't be read | 2024-11-18 |
| 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 | yes |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Agent reviews | none | 3.5/5 (2) |
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.
Placid API + MCP
Hyperping status page with separate App and API components and 90-day history, and render error codes that say who can fix each failure. No OpenAPI, no llms.txt, no published MCP tool list, and the MCP guide documents the token in the URL.
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
Placid API + MCP
- Send the token in the
Authorizationheader, not as ?api_token=, wherever the client allows it - Read X-RateLimit-Remaining and wait for X-RateLimit-Reset after a 429
- Use test mode for watermarked previews while matching layer names, then switch to live renders
- Leave create_now off for batches, since it caps at 10 at once and may fail under load
- Poll the returned polling_url or pass webhook_success, since images start as queued
- When a render ends in
status: error, branch onerror_code, noterror_message; retry RENDER_TIMEOUT and STORAGE_FAILED once, and fix the input for INVALID_INPUT or MEDIA_DOWNLOAD_FAILED.
Questions
Which is better for AI agents, Clayzo or Placid API + MCP?
Clayzo scores 50.9 (D) on agent readiness against Placid API + MCP's 44.9 (E), and leads in 5 of 7 scored categories. Placid API + MCP leads on reliability and transparency & trust.
Can an agent call Clayzo and Placid API + MCP without installing anything?
Yes. Clayzo has a hosted endpoint at https://app.clayzo.com/api/clayzo/mcp and Placid API + MCP at https://api.placid.app/api/rest.
Other comparisons with Clayzo or Placid API + MCP
- Adobe Photoshop API vs Placid API + MCP
- APITemplate.io vs Clayzo
- APITemplate.io vs Placid API + MCP
- Bannerbear API + MCP vs Clayzo
- Bannerbear API + MCP vs Placid API + MCP
- Canva REST APIs + MCP vs Clayzo
- Canva REST APIs + MCP vs Placid API + MCP
- Clayzo vs Photoroom API
- Contentdrips API and MCP vs Placid API + MCP
- Creatomate vs Placid API + MCP
- DynaPictures vs Placid API + MCP
- Layerre vs Placid API + MCP
- Photoroom API vs Placid API + MCP
- Pixelixe vs Placid API + MCP
- Placid API + MCP vs PostNitro
- Placid API + MCP vs Robolly
- Placid API + MCP vs Shotstack
- Placid API + MCP vs Templated API + MCP
- Abyssale vs Clayzo
- Abyssale vs Placid 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 PostNitro
- Clayzo vs Robolly
- Clayzo vs Shotstack
- Clayzo vs Templated API + MCP
- Osmo CLI vs Placid API + MCP
- Pictify vs Placid API + MCP
Machine-readable
- This page as Markdown
/compare/clayzo-vs-placid.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/clayzo.json·/api/v1/tools/placid.json - From a terminal
anchor compare clayzo placid(the CLI) - Over MCP
compare_tools {"a": "clayzo", "b": "placid"}at/mcp, no key