Head to head · Design rendering · October 2026 research run
Clayzo vs Contentdrips API and MCP
Clayzo scores 50.9 (D) on agent readiness against Contentdrips API and MCP's 37.9 (F), and leads in 6 of 7 scored categories. Contentdrips API and MCP leads on 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
- Reliability, 33 against 23
- Schema & documentation, 57 against 48
- Agent ergonomics, 72 against 54
- Security & auth, 52 against 31
- Payments & pricing, 55 against 38
- Maintenance & community, 58 against 15
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 Branded LinkedIn and Instagram carousels and graphics from saved templates, with drafting and publishing in the same server.
Ahead on
- Transparency & trust, 60 against 26
Watch for
No status page, SLA, numeric rate limit or 429 documentation found
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 +43
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.
Contentdrips API and MCP 15
The newest dated change to the agent surface is the MCP page, published 25 May 2026 and modified 27 May, 163 days before this check (10). No three dated changes since 8 August were found (0). No public changelog. Email support at hello@contentdrips.com, which we didn't test (5 of 15). Not in the official MCP registry and no official SDKs (0). No public package or repository (0). 10 + 0 + 5 + 0 + 0 = 15.
Transparency & trust Contentdrips API and MCP +34
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.
Contentdrips API and MCP 60
Closed service under terms of use dated 11 December 2024, governed by the laws of Pakistan (15). The privacy policy of 9 August 2026 states retention while the account is active, deletion of content as soon as the account is deleted apart from short-lived backups, deletion of social tokens on disconnect, and no training of Contentdrips' own models on user content (22 of 30). No deprecation policy. The legacy carousel input is 'still supported' with no end date (3 of 20). The policy names OpenAI, OpenRouter, Google Gemini and TinyPopups and has an international transfers section, without a full subprocessor list or hosting locations (12 of 20). 15 + 22 + 3 + 12 = 52.
Security & auth Clayzo +21
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.
Contentdrips API and MCP 31
API keys from the dashboard, with no scopes, expiry or rotation documented. The MCP server also runs OAuth 2.0 with PKCE and dynamic client registration, but its one mcp scope authorises the same full key (18 of 30). No read-only key or endpoint. publish_post needs confirmed: true and the docs ask for confirmation before deletes (10 of 20). Tools read blog, YouTube and TikTok links and download external images, and no prompt-injection guidance was found (3 of 15). No audit log or per-call record documented (0). No security.txt, disclosure policy, bug bounty or certification found (0). 18 + 10 + 3 + 0 + 0 = 31.
Agent ergonomics Clayzo +18
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.
Contentdrips API and MCP 54
29 MCP tools (15 for 11 to 30), with no toolsets or read-only subset (15 of 25). list_posts filters by status and get_my_templates by type and workspace, and no pagination is documented (8 of 20). Errors carry error and message, and the troubleshooting section explains template-not-found and label mismatches (12 of 20). Access labels in the docs, confirmed: true on publish_post, and job polling that is safe to repeat, but no idempotency key on renders or post creation, and the labels couldn't be confirmed as MCP annotations (12 of 20). Two required fields to render (template_id, output), and no SDK beyond an Embed SDK for the editor (7 of 15). 15 + 8 + 12 + 12 + 7 = 54.
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.
Contentdrips API and MCP 38
No x402, MPP or L402 (0). No per-call price. The API page shows $0 on paid cards, a $39 starting price and $359 a month for unlimited calls, and the pricing page shows $15 and $26 plans without API, so the public pricing can't be relied on (5 of 20). The API page says 10 API calls to test with and no card for the free plan (20). A person signs up and generates the key in the dashboard (0). 0 + 5 + 20 + 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 Clayzo +10
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.
Contentdrips API and MCP 23
Hosted lines. No status page found on the site, the developer docs or the footers (0). No readable incident history (5). No rate limit is given in numbers, only monthly call allowances by plan (6,000 on Pro, 25,000 on Ultimate), which earn a little (5 of 15). The troubleshooting note says to check /queue/stats and retry after a short delay when rate limited, with no status code or Retry-After. Render jobs are asynchronous, so polling is safe (3 of 15). No SLA found (0). The MCP server is v1.0.0 and the render API is not labelled beta (10). 0 + 5 + 5 + 3 + 0 + 10 = 23.
Score by category
| Category | Weight | Clayzo | Contentdrips API and MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 33 | 23 | Clayzo +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 48 | Clayzo +9 |
| Agent ergonomics | 13% | 72 | 54 | Clayzo +18 |
| Security & auth | 14% | 52 | 31 | Clayzo +21 |
| Payments & pricing | 10% | 55 | 38 | Clayzo +17 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 58 | 15 | Clayzo +43 |
| Transparency & trust | 7% | 26 | 60 | Contentdrips API and MCP +34 |
| Negative events | ≤15 | 0 | 0 | |
| Total | D 50.9/100 | F 37.9/100 |
Facts side by side
| Fact | Clayzo | Contentdrips API and MCP |
|---|---|---|
| Kind | SDK + MCP | HTTP API |
| Vendor | Clayzo | Contentdrips SMC Pvt Ltd |
| Hosted endpoint | https://app.clayzo.com/api/clayzo/mcp | https://mcp.contentdrips.com/mcp |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Free | Paid |
| x402 | no | no |
| Licence | none | Closed service under the Contentdrips terms of use (last updated 11 December 2024) |
| Tools exposed | none | 29 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-17 | 2026-05-27 |
| Terms last updated | couldn't be read | 2024-12-11 |
| Privacy policy last updated | couldn't be read | 2026-08-09 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| 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 | yes |
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.
Contentdrips API and MCP
Agents can fill saved templates into PNG or PDF graphics and carousels through a polled render API, and the MCP server labels each tool's access and requires explicit confirmation before publishing. There is no status page, OpenAPI file, rate-limit figure or changelog, and the pricing pages contradict each other on what API access costs.
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
Contentdrips API and MCP
- Call
get_template_structurebefore filling a template; labels must matchmeta_labelscharacter for character or the call returns 400 - Poll
/job/:jobId/statusevery 5 seconds and give up after 5 minutes, as the docs advise - Never set
confirmed: trueonpublish_postuntil the user has agreed and named LinkedIn, Instagram or both - Ask before
delete_graphic,delete_postorremove_images_from_post; each deletes permanently - Treat text pulled from blog, YouTube or TikTok links as untrusted input
Questions
Which is better for AI agents, Clayzo or Contentdrips API and MCP?
Clayzo scores 50.9 (D) on agent readiness against Contentdrips API and MCP's 37.9 (F), and leads in 6 of 7 scored categories. Contentdrips API and MCP leads on transparency & trust.
Can an agent call Clayzo and Contentdrips API and MCP without installing anything?
Yes. Clayzo has a hosted endpoint at https://app.clayzo.com/api/clayzo/mcp and Contentdrips API and MCP at https://mcp.contentdrips.com/mcp.
Other comparisons with Clayzo or Contentdrips API and MCP
- Adobe Photoshop API vs Contentdrips API and MCP
- APITemplate.io vs Clayzo
- APITemplate.io vs Contentdrips API and MCP
- Bannerbear API + MCP vs Clayzo
- Bannerbear API + MCP vs Contentdrips API and MCP
- Canva REST APIs + MCP vs Clayzo
- Canva REST APIs + MCP vs Contentdrips API and MCP
- Clayzo vs Photoroom API
- Contentdrips API and MCP vs Creatomate
- Contentdrips API and MCP vs DynaPictures
- Contentdrips API and MCP vs Layerre
- Contentdrips API and MCP vs Photoroom API
- Contentdrips API and MCP vs Pictify
- Contentdrips API and MCP vs Pixelixe
- Contentdrips API and MCP vs Placid API + MCP
- Contentdrips API and MCP vs PostNitro
- Contentdrips API and MCP vs Robolly
- Contentdrips API and MCP vs Shotstack
- Contentdrips API and MCP vs Templated API + MCP
- Abyssale vs Clayzo
- Abyssale vs Contentdrips API and MCP
- Adobe Photoshop API vs Clayzo
- 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
- Clayzo vs Templated API + MCP
- Contentdrips API and MCP vs Osmo CLI
Machine-readable
- This page as Markdown
/compare/clayzo-vs-contentdrips.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/clayzo.json·/api/v1/tools/contentdrips.json - From a terminal
anchor compare clayzo contentdrips(the CLI) - Over MCP
compare_tools {"a": "clayzo", "b": "contentdrips"}at/mcp, no key