# Photoroom API vs Robolly (slim)

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

- Full: https://www.anchorterminal.com/compare/photoroom-vs-robolly.md (~4,900 tokens) · this version ~2,880 tokens · JSON https://www.anchorterminal.com/compare/photoroom-vs-robolly.json · canonical https://www.anchorterminal.com/compare/photoroom-vs-robolly
- 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)

Photoroom API scores 53.5 (D) on agent readiness against Robolly's 48.4 (D), and leads in 5 of 7 scored categories. Robolly leads on reliability and agent ergonomics. Both do design templates.

- Photoroom API: D 53.5, rank #946 of 1510 · https://www.anchorterminal.com/tools/photoroom.min.md
- Robolly: D 48.4, rank #1127 of 1510 · https://www.anchorterminal.com/tools/robolly.min.md
- 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 Schema & documentation, 86 against 57; Payments & pricing, 40 against 35; Maintenance & community, 13 against 5; Transparency & trust, 69 against 49.
- Robolly, 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 42; Agent ergonomics, 75 against 64. Also Free to start without a card.

| Category | Photoroom API | Robolly |
| --- | --- | --- |
| Reliability (16%) | 42 | 48 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 86 | 57 |
| Agent ergonomics (13%) | 64 | 75 |
| Security & auth (14%) | 49 | 47 |
| Payments & pricing (10%) | 40 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 13 | 5 |
| Transparency & trust (7%) | 69 | 49 |

| Fact (where they differ) | Photoroom API | Robolly |
| --- | --- | --- |
| Vendor | Photoroom | Avantis Innovations LLC (Robolly) |
| Hosted endpoint | `https://image-api.photoroom.com/v2` | `https://api.robolly.com/v1` |
| Pricing | Freemium | Paid |
| Licence | Proprietary service under the Photoroom Terms and Conditions. The sample code repository is MIT | Closed service under the Robolly terms of use (effective 8 April 2026) |
| Tools exposed | 1 | 9 |
| Last release | 2026-04-21 | none |
| Terms last updated | 2026-07-29 | 2026-04-08 |
| Privacy policy last updated | 2026-03-01 | 2026-04-08 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |

Why the edge:
- Schema & documentation, Photoroom API +29: 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).); Robolly 57 (No OpenAPI or other machine-readable contract found for the REST API, and the MCP server is closed. The MCP page lists all nine tools and `get_template_modifications` returns each template's keys, constraints and examples at run time (8 of 25, on that partial evidence). llms.txt indexes the docs (10). The MCP page says what each tool does, which tools change templates or spend credits, and that there is no delete tool (14 of 20). Modification keys follow `{element-name}.{modification-key}` with constraints from the template rather than a fixed schema (7 of 15). Request examples throughout and an error code table with eight codes (13 of 15). /v1 paths with no changelog (5 of 15). 8 + 10 + 14 + 7 + 13 + 5 = 57.)
- Transparency & trust, Photoroom API +20: 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).); 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.)
- Agent ergonomics, Robolly +11: 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).); Robolly 75 (Nine MCP tools (25). The renders list pages with a cursor, and templates are found by name (14 of 20). Errors carry `errorCode` and `developerMessage` with eight documented codes (17 of 20). Identical renders are cached for 45 days, so repeats are free and safe, the MCP server has no delete tool, and annotations couldn't be read on the closed server (12 of 20). Renders return the file synchronously by default, but there's no SDK (7 of 15). 25 + 14 + 17 + 12 + 7 = 75.)
- Maintenance & community, Photoroom API +8: 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).); 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.)
- Reliability, Robolly +6: 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).); 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.)
- Payments & pricing, Photoroom API +5: 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).); Robolly 35 (No x402, MPP or L402 (0). Plan prices are public and a table gives the credit cost of each format and size (15 of 20). 7-day trial with no card (20). A person signs up, then copies the key or approves OAuth (0). 0 + 15 + 20 + 0 = 35.)