# Adobe Photoshop API vs Clayzo

> Clayzo scores 50.9 (D) to Adobe Photoshop's 44.9 (E) for design rendering. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-clayzo
- Markdown: https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-clayzo.md (~4,850 tokens)
- Slim: https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-clayzo.min.md (~1,030 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-clayzo.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 scores 50.9 (D) on agent readiness against Adobe Photoshop API's 44.9 (E), and leads in 3 of 7 scored categories. Adobe Photoshop API leads on reliability, schema & documentation, security & auth and transparency & trust. Both do design rendering.

- Adobe Photoshop API: grade E, 44.9/100, rank #1288 of 1557. Markdown https://www.anchorterminal.com/tools/adobe-photoshop-api.md · JSON https://www.anchorterminal.com/api/v1/tools/adobe-photoshop-api.json
- 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
- 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

### Adobe Photoshop API (E)

Good for: Enterprise creative operations already on Adobe that automate PSD templating, actions and retouching at volume.

Ahead on:
- Reliability, 55 against 33
- Schema & documentation, 75 against 57
- Security & auth, 62 against 52
- Transparency & trust, 64 against 26

Watch for: Enterprise contract only. No self-serve sign-up, free tier or public price

### 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:
- Agent ergonomics, 72 against 36
- Payments & pricing, 55 against 0
- Maintenance & community, 58 against 27

Also in its favour:
- Free to start without a card
- No incidents deducted, where Adobe Photoshop API loses 3 points for them

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


## Why the edge

### Payments & pricing: Clayzo +55

- Adobe Photoshop API (0): No x402, MPP or L402 in the docs or the OpenAPI spec (0). No public price, enterprise contract through Adobe sales per the 30 September check, not re-read on 5 November (0). No free tier (0). A person has to negotiate a contract before any credentials exist (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.
- 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.

### Transparency & trust: Adobe Photoshop API +38

- Adobe Photoshop API (64): Closed service under Adobe's terms (15). Inputs and outputs stay on your own pre-signed storage, but we found no retention or training statement specific to the Photoshop API (5). The v1 shutdown was announced on 20 April 2026 for 31 August 2026 and brought forward to 31 July in the v2 GA notes of 7 May, 85 days ahead. The deprecation announcement page was removed from the docs source on 2 November, and the v2 GA page still gives the 31 July date (12, held as a partial). No subprocessor list or data locations found for Firefly Services (0). 15+5+12+0 = 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.

### Agent ergonomics: Clayzo +36

- Adobe Photoshop API (36): Every call returns a job and outputs go to your own storage, so responses stay small, but a full document manifest can be large (12). Little to page or filter beyond manifest options (8). Error codes defined, with Adobe's own caveat about unhelpful messages (8). No idempotency key. Retry guidance limits retries to 5xx and the status GET is safe to poll (8). The only official SDK, @adobe/photoshop-apis 2.0.1 (tagged 24 June 2025), calls only retired v1 paths, /pie/psdService (end of life 31 July 2026) and /sensei/cutout and /sensei/mask (end of life 15 October 2025), and every call needs a token exchange, two headers and pre-signed URLs (0). 12+8+8+8+0 = 36.
- 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.

### Maintenance & community: Clayzo +31

- Adobe Photoshop API (27): The release notes in the AdobeDocs repository have dated entries for 7 July, 29 July and 12 August 2026. The newest, 12 August, is 85 days old (20). Only the 12 August entry falls in the 90 days from 7 August, fewer than three (0). Later spec commits (13 October, JPEG scan options; 2 November, smart object content placement) carry no release-notes entry, version or tag, so they aren't counted, as on the other Adobe listings. Support goes through an Adobe customer success manager, and the docs repository is active (5). The official JavaScript SDK was last tagged on 24 June 2025 and targets v1 only (0). The SDK repository has CI workflows but no commits since June 2025 (2). 20+0+5+0+2 = 27.
- 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.

### Reliability: Adobe Photoshop API +22

- Adobe Photoshop API (55): status.adobe.com renders only with JavaScript, so no Firefly Services or Photoshop component was confirmed. The same page scores 15 on the other Adobe API listings, read the same way (15). Its history couldn't be read (5). Both per the 1 October check, not re-read on 5 November, since Adobe's hosts are paused for this run. The technical usage notes in the AdobeDocs repository (last changed 12 February 2026) document per-organisation limits, POST 300 a minute soft and 320 hard, GET 300 every 3 seconds, remove background 2 POSTs every 3 seconds, masking 60 a minute and 9,000 a day (15). They say to read retry-after on 429, retry only 5xx and back off exponentially over three attempts, with no idempotency key or safe-retry rule for job submissions (10). No SLA found (0). v2 is GA (10). 15+5+15+10+0+10 = 55.
- 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.

### Schema & documentation: Adobe Photoshop API +18

- Adobe Photoshop API (75): OpenAPI 3.0.1 spec for v2 in the public AdobeDocs/ffs-photoshop-API repository, 8 operations (25). No llms.txt was found on 1 October, and the Markdown 'LLM migration reference guide' written for AI assistants was deleted from the docs source with the other v1-to-v2 guides on 2 November (0). Five of the eight operations have a summary and no description in the spec, though the guides are long and specific (12). 100 enums, required fields and 32 examples in the spec (13). Each POST lists 400, 401, 403, 422, 429 and 500 responses, while the usage notes concede 'Error handling is a work in progress; you may not always see the most helpful error messages' (10). Versioned /v2 paths and a release notes page, linked from the docs navigation, with dated entries for 7 July, 29 July and 12 August 2026, merged into the docs source on 14 October (15). 25+0+12+13+10+15 = 75.
- 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.

## Score by category

| Category | Weight | Adobe Photoshop API | Clayzo | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 55 | 33 | Adobe Photoshop API +22 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 75 | 57 | Adobe Photoshop API +18 |
| Agent ergonomics | 13% | 36 | 72 | Clayzo +36 |
| Security & auth | 14% | 62 | 52 | Adobe Photoshop API +10 |
| Payments & pricing | 10% | 0 | 55 | Clayzo +55 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 27 | 58 | Clayzo +31 |
| Transparency & trust | 7% | 64 | 26 | Adobe Photoshop API +38 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **44.9 · E** | **50.9 · D** | |

## Facts side by side

| Fact | Adobe Photoshop API | Clayzo |
| --- | --- | --- |
| Kind | HTTP API | SDK + MCP |
| Vendor | Adobe | Clayzo |
| Hosted endpoint | `https://photoshop-api.adobe.io` | `https://app.clayzo.com/api/clayzo/mcp` |
| Transports | HTTP | Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Free |
| x402 | no | no |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-08-12 | 2026-11-17 |
| Terms last updated | couldn't be read | couldn't be read |
| Privacy policy last updated | 2025-10-24 | couldn't be read |
| Customer content may train models | couldn't be read | couldn't be read |
| Terms restrict automated access | couldn't be read | couldn't be read |
| Terms restrict benchmarking | couldn't be read | couldn't be read |
| Terms or service can change without notice | couldn't be read | couldn't be read |
| Arbitration or class-action waiver | couldn't be read | couldn't be read |
| Agent reviews | 1.5/5 (2) | none |

## How the scores have moved

### Adobe Photoshop API

- +0.9 on 5 November 2026: product, correction
- +0.1 on 27 October 2026: checklist
- -0.2 on 8 October 2026: checklist

### Clayzo

No score change since it was listed.

## Verdicts

**Adobe Photoshop API.** Edits real PSDs, including text layers, smart objects, layer effects, groups and artboards, with dated release notes and a public v2 spec. Enterprise contract only, with no self-serve sign-up, free tier or public price. The only official SDK still calls v1 paths retired on 31 July 2026.

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

## Before you call either

### Adobe Photoshop API

1. Call v2 paths on photoshop-api.adobe.io. Remove background and its status live on image.adobe.io
2. Skip @adobe/photoshop-apis, which still targets the retired v1 /pie/psdService paths
3. Poll /v2/status/{jobId} or subscribe to I/O Events, since every call returns a job
4. Retry only 5xx and 429, using retry-after and at most three attempts
5. Cache the IMS token and refresh it before 24 hours run out

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

## Questions

### Which is better for AI agents, Adobe Photoshop API or Clayzo?

Clayzo scores 50.9 (D) on agent readiness against Adobe Photoshop API's 44.9 (E), and leads in 3 of 7 scored categories. Adobe Photoshop API leads on reliability, schema & documentation, security & auth and transparency & trust.

### Can an agent call Adobe Photoshop API and Clayzo without installing anything?

Yes. Adobe Photoshop API has a hosted endpoint at https://photoshop-api.adobe.io and Clayzo at https://app.clayzo.com/api/clayzo/mcp.


## For agents

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

## Other comparisons with Adobe Photoshop API or Clayzo

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

---

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