# Clayzo vs Robolly

> Clayzo and Robolly score within a point of each other for design rendering, 50.9 and 50.6 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/clayzo-vs-robolly
- Markdown: https://www.anchorterminal.com/compare/clayzo-vs-robolly.md (~3,800 tokens)
- Slim: https://www.anchorterminal.com/compare/clayzo-vs-robolly.min.md (~880 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/clayzo-vs-robolly.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-18

Clayzo and Robolly score within a point of each other on agent readiness, 50.9 (D) and 50.6 (D). Robolly leads on reliability and transparency & trust. Both do design rendering.

- Clayzo: grade D, 50.9/100, rank #1137 of 1557. Markdown https://www.anchorterminal.com/tools/clayzo.md · JSON https://www.anchorterminal.com/api/v1/tools/clayzo.json
- Robolly: grade D, 50.6/100, rank #1146 of 1557. Markdown https://www.anchorterminal.com/tools/robolly.md · JSON https://www.anchorterminal.com/api/v1/tools/robolly.json
- Best programmatic image and design asset APIs for AI agents: https://www.anchorterminal.com/best/design-assets/index.md
- All 171 assets comparisons: https://www.anchorterminal.com/compare/design-assets/index.md

## Which one, for what

### Clayzo (D)

Good for: Coding agents that make motion graphics, product animations or interactive web animations for a user's own site or app.

Ahead on:
- Security & auth, 52 against 47
- Maintenance & community, 58 against 5

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

### Robolly (D)

Good for: Template-driven images, PDFs and short videos for marketers and developers who want a hosted editor and simple synchronous calls.

Ahead on:
- Reliability, 48 against 33
- Transparency & trust, 49 against 26

Watch for: No OpenAPI or other machine-readable contract found


## Why the edge

### Maintenance & community: Clayzo +53

- 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.
- Robolly (5): No changelog, release notes or dated API change was found. The sitemap marks every docs page as modified on 4 November 2026, which reads as a site rebuild rather than a change, so it isn't counted (0). No dated changes since 8 August (0). Support by email, with chat on higher plans; not tested (5 of 15). Not in the official MCP registry and no SDKs (0). No public package or repository (0). 0 + 0 + 5 + 0 + 0 = 5.

### Transparency & trust: Robolly +23

- 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.
- Robolly (49): Closed service under terms effective 8 April 2026 from Avantis Innovations LLC in Wyoming. The terms can change without notice (15). The privacy policy of the same date covers Google sign-in and Sheets data, says spreadsheet rows aren't kept beyond a render and account data is deleted with the account, and otherwise names no periods (10 of 30). No deprecation policy or notices (0). Hosting is described only as third-party vendors, with no processors or locations named, while the footer says Made in EU (2 of 20). 15 + 10 + 0 + 2 = 27.

### Reliability: Robolly +15

- 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.
- Robolly (48): Hosted lines. The footer links an UptimeRobot status page, but it loads its figures from /api/, which stats.uptimerobot.com's robots.txt disallows, so the page showed no monitors or history (10 of 20 for a page that exists) and no history was read (5). A hard limit of 3 renders a second is published (15). The `rate-limit` error code and advice to send renders one at a time, and identical renders are cached for 45 days at no cost, which makes a retry safe; there's no Retry-After or backoff interval (8 of 15). No SLA found (0). The API isn't labelled beta (10). 10 + 5 + 15 + 8 + 0 + 10 = 48.

### Security & auth: Clayzo +5

- 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.
- Robolly (47): Bearer API key, signed render links, and MCP OAuth with one `robolly:mcp` scope limited to the organisation the user approves. Connections are listed and revoked under Connected AI Tools, and the API key is never shared with an OAuth client. No key scopes or rotation documented (22 of 30). The MCP server can create and update templates but not delete them; there's no read-only mode (10 of 20). Tools return the user's templates and public gallery designs (10 of 15). A renders list and the connected-tools view give some visibility, with no audit log documented (5 of 15). No security.txt (the path returns the site's HTML shell), disclosure policy, bug bounty or certification (0). 22 + 10 + 10 + 5 + 0 = 47.

## Score by category

| Category | Weight | Clayzo | Robolly | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 33 | 48 | Robolly +15 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 57 | 57 | even |
| Agent ergonomics | 13% | 72 | 75 | Robolly +3 |
| Security & auth | 14% | 52 | 47 | Clayzo +5 |
| Payments & pricing | 10% | 55 | 53 | Clayzo +2 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 58 | 5 | Clayzo +53 |
| Transparency & trust | 7% | 26 | 49 | Robolly +23 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **50.9 · D** | **50.6 · D** | |

## Facts side by side

| Fact | Clayzo | Robolly |
| --- | --- | --- |
| Kind | SDK + MCP | HTTP API |
| Vendor | Clayzo | Avantis Innovations LLC (Robolly) |
| Hosted endpoint | `https://app.clayzo.com/api/clayzo/mcp` | `https://api.robolly.com/v1` |
| 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 Robolly terms of use (effective 8 April 2026) |
| Tools exposed | none | 9 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-11-17 | none |
| Terms last updated | couldn't be read | 2026-04-08 |
| Privacy policy last updated | couldn't be read | 2026-04-08 |
| 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 | yes |

## How the scores have moved

### Clayzo

No score change since it was listed.

### Robolly

- +2.2 on 13 November 2026: checklist

## 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.

**Robolly.** Robolly's nine MCP tools, synchronous renders, typed error codes and free cached re-renders keep template rendering cheap and predictable for an agent, and OAuth connections can be revoked per client. There is no OpenAPI file, changelog or dated release, and API access starts at $39 a month after a 7-day trial.

## 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

### Robolly

1. Call `get_template_modifications` before `render` to learn the keys a template accepts
2. Send renders one at a time; the API refuses more than 3 a second with `rate-limit`
3. Repeat an identical render freely; it is cached for 45 days and costs nothing
4. Poll `get_render` after `render_video`, since video renders are queued
5. Stop on `render-limit-exhausted` and tell the user the monthly credits are spent

## Questions

### Which is better for AI agents, Clayzo or Robolly?

Clayzo and Robolly score within a point of each other on agent readiness, 50.9 (D) and 50.6 (D). Robolly leads on reliability and transparency & trust.

### Can an agent call Clayzo and Robolly without installing anything?

Yes. Clayzo has a hosted endpoint at https://app.clayzo.com/api/clayzo/mcp and Robolly at https://api.robolly.com/v1.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/clayzo-vs-robolly.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clayzo-vs-robolly.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "clayzo", "b": "robolly"}`. From a terminal: `anchor compare clayzo robolly`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clayzo.json and https://www.anchorterminal.com/api/v1/tools/robolly.json

## Other comparisons with Clayzo or Robolly

- [Adobe Photoshop API vs Robolly](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-robolly.md)
- [APITemplate.io vs Clayzo](https://www.anchorterminal.com/compare/apitemplate-io-vs-clayzo.md)
- [APITemplate.io vs Robolly](https://www.anchorterminal.com/compare/apitemplate-io-vs-robolly.md)
- [Bannerbear API + MCP vs Clayzo](https://www.anchorterminal.com/compare/bannerbear-vs-clayzo.md)
- [Bannerbear API + MCP vs Robolly](https://www.anchorterminal.com/compare/bannerbear-vs-robolly.md)
- [Canva REST APIs + MCP vs Clayzo](https://www.anchorterminal.com/compare/canva-vs-clayzo.md)
- [Canva REST APIs + MCP vs Robolly](https://www.anchorterminal.com/compare/canva-vs-robolly.md)
- [Clayzo vs Photoroom API](https://www.anchorterminal.com/compare/clayzo-vs-photoroom.md)
- [Contentdrips API and MCP vs Robolly](https://www.anchorterminal.com/compare/contentdrips-vs-robolly.md)
- [Creatomate vs Robolly](https://www.anchorterminal.com/compare/creatomate-vs-robolly.md)
- [DynaPictures vs Robolly](https://www.anchorterminal.com/compare/dynapictures-vs-robolly.md)
- [Layerre vs Robolly](https://www.anchorterminal.com/compare/layerre-vs-robolly.md)
- [Photoroom API vs Robolly](https://www.anchorterminal.com/compare/photoroom-vs-robolly.md)
- [Pixelixe vs Robolly](https://www.anchorterminal.com/compare/pixelixe-vs-robolly.md)
- [Placid API + MCP vs Robolly](https://www.anchorterminal.com/compare/placid-vs-robolly.md)
- [PostNitro vs Robolly](https://www.anchorterminal.com/compare/postnitro-vs-robolly.md)
- [Robolly vs Shotstack](https://www.anchorterminal.com/compare/robolly-vs-shotstack.md)
- [Robolly vs Templated API + MCP](https://www.anchorterminal.com/compare/robolly-vs-templated.md)
- [Abyssale vs Clayzo](https://www.anchorterminal.com/compare/abyssale-vs-clayzo.md)
- [Abyssale vs Robolly](https://www.anchorterminal.com/compare/abyssale-vs-robolly.md)
- [Adobe Photoshop API vs Clayzo](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-clayzo.md)
- [Clayzo vs Contentdrips API and MCP](https://www.anchorterminal.com/compare/clayzo-vs-contentdrips.md)
- [Clayzo vs Creatomate](https://www.anchorterminal.com/compare/clayzo-vs-creatomate.md)
- [Clayzo vs DynaPictures](https://www.anchorterminal.com/compare/clayzo-vs-dynapictures.md)
- [Clayzo vs Layerre](https://www.anchorterminal.com/compare/clayzo-vs-layerre.md)
- [Clayzo vs Osmo CLI](https://www.anchorterminal.com/compare/clayzo-vs-osmo-cli.md)
- [Clayzo vs Pictify](https://www.anchorterminal.com/compare/clayzo-vs-pictify.md)
- [Clayzo vs Pixelixe](https://www.anchorterminal.com/compare/clayzo-vs-pixelixe.md)
- [Clayzo vs Placid API + MCP](https://www.anchorterminal.com/compare/clayzo-vs-placid.md)
- [Clayzo vs PostNitro](https://www.anchorterminal.com/compare/clayzo-vs-postnitro.md)
- [Clayzo vs Shotstack](https://www.anchorterminal.com/compare/clayzo-vs-shotstack.md)
- [Clayzo vs Templated API + MCP](https://www.anchorterminal.com/compare/clayzo-vs-templated.md)
- [Osmo CLI vs Robolly](https://www.anchorterminal.com/compare/osmo-cli-vs-robolly.md)
- [Pictify vs Robolly](https://www.anchorterminal.com/compare/pictify-vs-robolly.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
