Head to head · Design templates · October 2026 research run

Clayzo vs Photoroom API

Photoroom API scores 56 (C) on agent readiness against Clayzo's 50.9 (D), and leads in 4 of 7 scored categories. Clayzo leads on agent ergonomics and maintenance & community. Both do design templates.

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 64
  • Maintenance & community, 58 against 13

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

Photoroom API C

Best for Product-photo work at volume, such as cutouts, white backgrounds, shadows, generated scenes and clothing shots, one image a call.

Ahead on

  • Reliability, 42 against 33
  • Schema & documentation, 86 against 57
  • Payments & pricing, 60 against 55
  • Transparency & trust, 69 against 26

Watch for

No status page was found on the site or in the docs, so there is no public incident history to read

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 +45

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.

Photoroom API 13

The last dated changelog entry is 21 April 2026 by the 9 October reading, 197 days before 4 November. The changelog sits on a paused host and was not re-read (0, cause time). No dated changelog entry in the 90 days from 6 August by that reading, and no other dated Photoroom source was found (0). A public changelog and a Discourse community where each of the 17 topics dated 30 September to 3 October 2026 had a reply, per the 9 October check. We did not open the topics to see who replied (11). No official SDK, and the official MCP registry search for photoroom returned no entry on 4 November (0). The sample code repository's last commit is a README change on 23 April 2026 and it has no CI, per a clone on 4 November (2).

Transparency & trust Photoroom API +43

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.

Photoroom API 69

Per the 9 October check, not re-read on 4 November. Closed hosted service under the Photoroom Terms and Conditions effective 29 July 2026, which name the application programming interface. Sample code is MIT (15). The security page gives retention figures (images discarded after the call, operational logs 15 days, API access logs one year). The statements on training disagree. The privacy policy of March 2026 says model improvement does not apply to API images, the security page says self-serve API plans train by default with an opt-out, and the terms authorise training on user content with an opt-out. A DPA is for Enterprise customers only (14). Preview and alpha functions carry a two-week notice, the 2024 base URL change gave a dated deadline, and the AI Backgrounds v2 model is marked deprecated with no removal date (12). The security page names GCP, AWS, Cloudflare, Datadog and Vercel and says hosting is in the United States. The full list is in the trust centre, which was not read (16).

Schema & documentation Photoroom API +29

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.

Photoroom API 86

Per the 9 October check, not re-read on 4 November. A public OpenAPI 3.1.0 description at image-api.photoroom.com/openapi, read as embedded on the docs reference page, with four operations (25). llms.txt, a Markdown twin of every page and a page with a prompt written for coding agents (10). 86 of the 87 parameters of GET /v2/edit carry a description, the operation description lists every edit, and the agent page says when to call each of the two APIs (17). 31 of 87 parameters have enums, but booleans are strings, no field of /v2/edit is marked required, and the embedded description declares neither the x-api-key header nor the pr-* model headers (10). Curl examples on every page and 400, 402 and 500 bodies in the description. 401, 403 and 429 are documented in prose only, and the two APIs use different error shapes (11). Paths are /v1 and /v2, models are pinned by dated headers and the changelog is dated back to June 2023, but the description's version is fixed at 1.0.0 and the last changelog entry is 21 April 2026 (13).

Reliability Photoroom API +9

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.

Photoroom API 42

Read with the hosted lines. Photoroom's terms (clause 2.7.a, effective 29 July 2026) bar copying any part of the Services by automated or non-automated scraping, so photoroom.com hosts were not re-read on 4 November and the 9 October readings are kept. No status page was found on photoroom.com, the docs or the security page, and status.photoroom.com did not answer one request, per the 9 October check (0). With no history to read, the incident line takes the floor of 5. The security page states one incident on record, a 30-minute availability disruption in October 2024, which is the vendor's own account (5). Limits are published, 60 images a minute by default and 1,000 a month and 100 a day in sandbox mode (15). The docs say a 429 is returned at the limit, tell callers to back off exponentially and to retry a 500 up to three times, and say failed calls are not billed. No Retry-After header or idempotency key is documented, so safe-retry guidance without keys (12). The API page states a 99.9 per cent uptime target on Enterprise accounts, but no SLA document was found and the terms say availability is not guaranteed, so no SLA could be read (0). The Image Editing API left beta on 3 April 2024. Upscale, text-guided segmentation and templating are labelled preview (10).

Agent ergonomics Clayzo +8

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.

Photoroom API 64

Per the 9 October check, not re-read on 4 November. The response body is the image itself, so an agent saves a file and reads nothing into context. outputSize, maxWidth, maxHeight, export.format and the size presets set what comes back, and the MCP server has one tool, per Photoroom (18). Nothing to paginate. Output size, format and DPI controls (15). JSON errors with a message and a documented meaning for 400, 401, 403, 402, 429 and 500, but the two APIs use different shapes and Unauthorized covers both a missing key and an empty balance (13). No idempotency key. Calls keep no state, failed calls are not billed and background.seed repeats a generated background, but a retried success is billed again. The MCP tool's annotations were not read (10). Only the image is required and defaults are sensible. No official SDK, only sample code for four platforms (8).

Payments & pricing Photoroom API +5

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.

Photoroom API 60

Per the 9 October check, not re-read on 4 November. No x402, MPP or L402 in the docs, the OpenAPI description or the pricing pages (0). Per-image prices are public, $0.02 for background removal and $0.10 for an Image Editing call (20). Sandbox mode gives 1,000 free watermarked calls a month and a new account 10 free production calls on the Remove Background API, with no card, per the pricing page (20). A person has to create an account and activate the API in the dashboard. The MCP server also needs a Photoroom sign-in (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Score by category

CategoryWeightClayzoPhotoroom APIEdge
Reliability16%3342Photoroom API +9
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%5786Photoroom API +29
Agent ergonomics13%7264Clayzo +8
Security & auth14%5249Clayzo +3
Payments & pricing10%5560Photoroom API +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%5813Clayzo +45
Transparency & trust7%2669Photoroom API +43
Negative events≤1500
TotalD 50.9/100C 56/100

Facts side by side

FactClayzoPhotoroom API
KindSDK + MCPHTTP API
VendorClayzoPhotoroom
Hosted endpointhttps://app.clayzo.com/api/clayzo/mcphttps://image-api.photoroom.com/v2
TransportsStreamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreeFreemium
x402nono
LicencenoneProprietary service under the Photoroom Terms and Conditions. The sample code repository is MIT
Tools exposednone1
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-172026-04-21
Terms last updatedcouldn't be read2026-07-29
Privacy policy last updatedcouldn't be read2026-03-01
Customer content may train modelscouldn't be readyes, with an opt-out
Terms restrict automated accesscouldn't be readyes
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 readyes

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.

Photoroom API

A call costs $0.02 for background removal or $0.10 for any combination of edits, and a sandbox key gives 1,000 free watermarked calls a month without a card. No status page or official SDK was found, and Photoroom's privacy policy and security page disagree on whether API images train its models.

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

Photoroom API

  1. Send the key in the x-api-key header. Prefix it with sandbox_ while testing, because calls with the plain key consume paid images
  2. Save the response body as a file. A 200 returns image bytes, PNG by default, and any other status returns JSON with error.message or detail
  3. Send model selectors such as pr-ai-shadows-model-version: 2026-04-15 as HTTP headers, not form fields. They are not in the OpenAPI file
  4. Stay under 60 images a minute. On 429 back off with an exponential delay, and set a client timeout of at least 60 seconds for AI edits
  5. Use POST /v2/edit with imageFile for local files and GET /v2/edit with imageUrl for hosted ones. Each call takes one image

Questions

Which is better for AI agents, Clayzo or Photoroom API?

Photoroom API scores 56 (C) on agent readiness against Clayzo's 50.9 (D), and leads in 4 of 7 scored categories. Clayzo leads on agent ergonomics and maintenance & community.

Can an agent call Clayzo and Photoroom API without installing anything?

Yes. Clayzo has a hosted endpoint at https://app.clayzo.com/api/clayzo/mcp and Photoroom API at https://image-api.photoroom.com/v2.

Other comparisons with Clayzo or Photoroom API

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.