# Layerre vs Photoroom API (slim)

> Layerre scores 57.6 (C) to Photoroom's 53.5 (D) for design templates. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/layerre-vs-photoroom.md (~4,100 tokens) · this version ~2,080 tokens · JSON https://www.anchorterminal.com/compare/layerre-vs-photoroom.json · canonical https://www.anchorterminal.com/compare/layerre-vs-photoroom
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Layerre scores 57.6 (C) on agent readiness against Photoroom API's 53.5 (D), and leads in 3 of 7 scored categories. Photoroom API leads on payments & pricing and transparency & trust. Both do design templates.

- Layerre: C 57.6, rank #785 of 1486 · https://www.anchorterminal.com/tools/layerre.min.md
- Photoroom API: D 53.5, rank #940 of 1486 · https://www.anchorterminal.com/tools/photoroom.min.md
- Layerre, good for Bulk image and PDF variants from Canva designs a team already has. Ahead on Agent ergonomics, 69 against 64; Maintenance & community, 78 against 13. Also Runs on your own machine.
- Photoroom API, good for Product-photo work at volume, such as cutouts, white backgrounds, shadows, generated scenes and clothing shots, one image a call. Ahead on Payments & pricing, 40 against 25; Transparency & trust, 69 against 63.

| Category | Layerre | Photoroom API |
| --- | --- | --- |
| Reliability (16%) | 42 | 42 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 86 |
| Agent ergonomics (13%) | 69 | 64 |
| Security & auth (14%) | 48 | 49 |
| Payments & pricing (10%) | 25 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 78 | 13 |
| Transparency & trust (7%) | 63 | 69 |

| Fact (where they differ) | Layerre | Photoroom API |
| --- | --- | --- |
| Vendor | Layerre | Photoroom |
| Hosted endpoint | `https://api.layerre.com/v1` | `https://image-api.photoroom.com/v2` |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Licence | MIT for the MCP server. The Layerre API is a closed service under terms last updated 13 August 2026 | Proprietary service under the Photoroom Terms and Conditions. The sample code repository is MIT |
| Tools exposed | 13 | 1 |
| MCP registry | `com.layerre/layerre` | not listed |
| Last release | 2026-10-29 | 2026-04-21 |
| Terms last updated | no date given | 2026-07-29 |
| Privacy policy last updated | no date given | 2026-03-01 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict automated access | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 119 npm/wk | none |

Why the edge:
- Maintenance & community, Layerre +65: Layerre 78 (@layerre/mcp-server 0.1.0 published to npm on 29 October 2026, 8 days before this check (30). MCP server commits from 19 to 24 October, the registry entry of 29 October, and What's New entries dated 21 August and 18 October in the sitemap (20). The repository is a week old with no issues to judge; support by email and in-app chat (5 of 25). com.layerre/layerre is in the official MCP registry under a domain-verified namespace (15). CI runs the vitest suite on push and pull requests to main on Node 22 (8 of 10). 30 + 20 + 5 + 15 + 8 = 78.); 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).)
- Payments & pricing, Photoroom API +15: Layerre 25 (No x402, MPP or L402 (0). Plan prices are public with render counts, and one import or one variant is one render, so the price a render follows from the plan (about $0.03 on Starter, $0.005 on Pro) without being published per unit (15 of 20). Free plan of 50 renders a month with API access; the pricing page doesn't say whether a card is needed (10 of 20, half as with an unstated card rule). A person signs up and creates the key, or approves OAuth in a browser (0). 0 + 15 + 10 + 0 = 25.); Photoroom API 40 (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).)
- Transparency & trust, Photoroom API +6: Layerre 63 (The MCP server is MIT. The service is closed under terms of 13 August 2026 that name a sole proprietorship in Ontario (20 of 30). The privacy policy and DPA of the same date agree. Data is kept while the account is active and deleted from production on account deletion, with limited backups. Design files aren't used to train public AI models. Google Analytics runs on accepted cookies (24 of 30). No deprecation policy or notice period (0). Ten subprocessors listed with purpose and location in both documents, including Supabase, Stripe, Cloudflare, Google, Resend, Canva and Slack (20). 20 + 24 + 0 + 20 = 64.); 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).)
- Agent ergonomics, Layerre +5: Layerre 69 (13 MCP tools (15 for 11 to 30), with no toolsets or read-only subset (15). Template and variant lists take `skip` and `limit`, and templates filter by `tag` and `q` and can leave out layers (16 of 20). 422 validation bodies and a JSON 429 with `retry_after` (17 of 20). Every tool is annotated, read tools with readOnlyHint and idempotentHint, updates idempotent, no tool destructive, and the server has no delete tool. The REST API has no idempotency keys for variant creation (16 of 20). Few required fields, but no official SDK; a Postman collection and the MCP package only (5 of 15). 15 + 16 + 17 + 16 + 5 = 69.); 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).)