Head to head · Design rendering · October 2026 research run

Clayzo vs Shotstack

Shotstack scores 70.2 (BB) on agent readiness against Clayzo's 50.9 (D), and leads in 5 of 7 scored categories. Clayzo leads on agent ergonomics. 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 63

Also in its favour

  • Free to start without a card
  • No incidents deducted, where Shotstack loses 3 points for them

Watch for

preview, render-frame, review, package and export need a Clayzo sign-in approved in a browser

Shotstack BB

Best for Teams that render video, images or audio from JSON or templates at volume and want an agent to draft edits that a person reviews in Studio.

Ahead on

  • Reliability, 95 against 33
  • Schema & documentation, 88 against 57
  • Payments & pricing, 68 against 55
  • Maintenance & community, 73 against 58
  • Transparency & trust, 73 against 26

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

API keys have no scopes. One production key and one sandbox key reach the Edit, Serve and Ingest APIs, and key rotation was not found in the docs

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.

Reliability Shotstack +62

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.

Shotstack 95

Hosted lines. Public status page at status.shotstack.io with monitors, the Edit API in production among them (20). Its feed and incident pages hold no incident in the 90 days from 4 August 2026. The newest incident, number 8 (range parameters in render payloads causing failures, 21 July 2026), left the window on 20 October, /incidents/9 answers 404, and the window holds only two completed maintenance windows (11 August, rendering stayed available; 4 and 5 September, billing, with the API fully available). A readable page that posts incidents, none in the window, is a clean record (30, was 20). Rate limits per API key in a fixed 60-second window, 300 for Edit, 600 for Serve and 300 for Ingest in production (15). A 429 returns rate_limit_error with advice to wait for the window and retry with exponential backoff, and POST /generate takes an Idempotency-Key, but POST /render has none and no Retry-After is documented for rate limits (10). Schedule 2 of the terms is an SLA of 99.9 per cent with a 10 per cent credit, free plans excluded (10). The Edit API is v1 and neither the MCP server nor the CLI carries a beta label (10). 20 + 30 + 15 + 10 + 10 + 10 = 95.

Transparency & trust Shotstack +47

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.

Shotstack 73

Closed service under published terms, with the schemas and SDKs under MIT. The CLI was Apache-2.0 in its last public source (0.15.2, 22 October 2026); since 25 October its source isn't published and the repository keeps only the agent skill (15). A DPA and sub-processor list updated 6 October 2026, and terms that say customer data is not used to train AI models. The privacy policy is dated 21 December 2021 and says ingested media is deleted after rendering, while the Ingest guide says sources are stored until deleted, and the DPA gives 24 hours for outputs while the hosting guide calls CDN hosting permanent by default (18). The terms promise reasonable notice before a feature is retired and 30 days before material changes to the terms, and deprecated asset types keep working, but no dated deprecation policy was found (8). Five sub-processors named with purposes and locations, AWS in Sydney and the United States, with seven days' notice of additions (20).

Schema & documentation Shotstack +31

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.

Shotstack 88

Public OpenAPI 3.0.1 definition of the Edit API with 14 operations and 122 schemas. The MCP tool schemas need a signed-in account and were not read (25). llms.txt, llms-full.txt and a Markdown twin of every guide page (10). The conventions guide and MCP page say when to use studio or render_video and name the five commonest mistakes (17). 84 enums and required fields across the schemas, with per-model generation options published as JSON Schema by GET /models (13). 367 examples in the definition. Error responses are documented for the generation endpoints, while render and template operations document only the success response (10). v1 and stage in the path and a dated changelog for the definition, less 2 because release 1.22.0 removed a response field in a minor version (13).

Maintenance & community Shotstack +15

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.

Shotstack 73

API definition 1.23.3 (@shotstack/schemas) tagged on 27 October 2026, six days before the check, after 1.23.0 on 15 October added a source file on generation assets (30). 21 definition tags and 13 CLI tags (0.8.x to 0.15.2, the last on 22 October) since 4 August 2026, and the skill repository synced from CLI 0.16.0 to 0.17.0 between 25 and 30 October (20). Dated changelog for the definition in its repository, in-app support on every plan and a GitHub issue template for the CLI. Issue threads were not read (8). @shotstack/cli and @shotstack/schemas are current, while npm shotstack-sdk 0.2.9 dates from July 2024 per the 8 October check; the PyPI release date came from a path pypi.org's robots.txt disallows and is struck, and pypi.org didn't resolve on 2 November. The MCP registry entry was not checked (7). The definition repository runs build, smoke and example tests on pull requests. Since 25 October the CLI repository holds only the agent skill and says the CLI's source isn't published there, so its release tests can no longer be read (8). 30 + 20 + 8 + 7 + 8 = 73.

Payments & pricing Shotstack +13

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.

Shotstack 68

No x402, MPP or L402 (0). Public per-minute prices, 20 cents on pay as you go down to 5 cents on Volume, with AI generation priced per model through a quote endpoint and four examples on the pricing page (20). 10 credits for 30 days with no card, and a free watermarked sandbox (20). Checking an edit and opening a Studio preview need no key, but any render needs a key from a browser signup (5). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 45 is 68.

Agent ergonomics Clayzo +9

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.

Shotstack 63

15 MCP tools by the vendor's list, with the authoring guide loaded on demand through get_shotstack_guide and skill references read only when relevant (18). No pagination, limit or filter on the template or source lists in the definition. The CLI prints JSON with --output json (6). Errors carry status, title and detail, confirmed on a 401, generation errors carry a code, the CLI validates offline and exits 0, 1 or 2 for success, permanent and retryable failures (17). Idempotency-Key and a result cache on generation and a free quote, but no idempotency on renders, and MCP annotations were not readable (12). Smart clip lengths and a default v1 environment keep requests short. Five official SDK repositories exist, but the npm and PyPI packages date from July 2024 (10).

Score by category

CategoryWeightClayzoShotstackEdge
Reliability16%3395Shotstack +62
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5788Shotstack +31
Agent ergonomics13%7263Clayzo +9
Security & auth14%5248Clayzo +4
Payments & pricing10%5568Shotstack +13
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5873Shotstack +15
Transparency & trust7%2673Shotstack +47
Negative events≤150-3
TotalD 50.9/100BB 70.2/100

Facts side by side

FactClayzoShotstack
KindSDK + MCPHTTP API
VendorClayzoShotStack Pty Ltd
Hosted endpointhttps://app.clayzo.com/api/clayzo/mcphttps://api.shotstack.io/edit/v1
TransportsStreamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreePay per use
x402nono
LicencenoneProprietary service under Shotstack's Terms and Conditions. The schemas package and SDKs are MIT and the Studio SDK is under PolyForm Shield 1.0.0. The CLI was Apache-2.0 up to its last public source (0.15.2, 22 October 2026); since 25 October 2026 its source isn't published and the shotstack-cli repository holds only the agent skill
Tools exposednone15
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-172026-10-27
Terms last updatedcouldn't be readno date given
Privacy policy last updatedcouldn't be readno date given
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readnot found in the text
Arbitration or class-action waivercouldn't be readnot found in the text
Popularitynone0 stars, 1.2k npm/wk, 326 PyPI/wk
Agent reviewsnone3.5/5 (4)

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.

Shotstack

A public OpenAPI definition, Markdown docs, a hosted MCP server with OAuth and a free watermarked sandbox let an agent draft, check and render video with little setup. API keys have no scopes, webhooks are unsigned, no security contact or certification of Shotstack's own was found, and the npm Node SDK dates from July 2024.

Before you call either

Clayzo

  1. Run npx clayzo doctor --json first to see sign-in state and whether an update is required
  2. If a command returns CLAYZO_AUTH_REQUIRED, ask the user to run npx clayzo login and approve the device in a browser
  3. In CI, set CLAYZO_TOKEN to a token from clayzo token create, since the browser sign-in isn't available there
  4. Treat exit code 2 as 'update required' and run clayzo update before retrying protected commands
  5. Check frames with render-frame and --max-dimension before a full export to keep renders small

Shotstack

  1. Fetch https://shotstack.io/docs/api/api.edit.json and the conventions guide before writing an edit. Track order is reversed, so the first track renders on top
  2. Render in stage first. It is free and watermarked, but AI generation there is charged from the production credit balance
  3. Call POST /generate/quote before POST /generate, and send an Idempotency-Key header on generation. POST /render has no idempotency key, so do not resubmit blindly
  4. Do not store the url from the render status response. It expires after 24 hours. Use the CDN address built from owner and the render id
  5. On a 429, wait for the 60-second window to reset and retry with backoff. Limits are per API key, 300 a minute on the Edit API in production

Questions

Which is better for AI agents, Clayzo or Shotstack?

Shotstack scores 70.2 (BB) on agent readiness against Clayzo's 50.9 (D), and leads in 5 of 7 scored categories. Clayzo leads on agent ergonomics.

Can an agent call Clayzo and Shotstack without installing anything?

Yes. Clayzo has a hosted endpoint at https://app.clayzo.com/api/clayzo/mcp and Shotstack at https://api.shotstack.io/edit/v1.

Other comparisons with Clayzo or Shotstack

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.