# Photoroom API vs Pictify (slim)

> Pictify scores 55.7 (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/photoroom-vs-pictify.md (~3,850 tokens) · this version ~1,880 tokens · JSON https://www.anchorterminal.com/compare/photoroom-vs-pictify.json · canonical https://www.anchorterminal.com/compare/photoroom-vs-pictify
- 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)

Pictify scores 55.7 (C) on agent readiness against Photoroom API's 53.5 (D), and leads in 4 of 7 scored categories. Photoroom API leads on transparency & trust. Both do design templates.

- Photoroom API: D 53.5, rank #940 of 1486 · https://www.anchorterminal.com/tools/photoroom.min.md
- Pictify: C 55.7, rank #856 of 1486 · https://www.anchorterminal.com/tools/pictify.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 Transparency & trust, 69 against 52. Also No incidents deducted, where Pictify loses 3 points for them.
- Pictify, good for HTML-to-image, template renders, PDFs and short video from one API, with per-render prices an agent can budget. Ahead on Agent ergonomics, 74 against 64; Maintenance & community, 68 against 13. Also Runs on your own machine; Free to start without a card.

| Category | Photoroom API | Pictify |
| --- | --- | --- |
| Reliability (16%) | 42 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 86 | 88 |
| Agent ergonomics (13%) | 64 | 74 |
| Security & auth (14%) | 49 | 45 |
| Payments & pricing (10%) | 40 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 13 | 68 |
| Transparency & trust (7%) | 69 | 52 |

| Fact (where they differ) | Photoroom API | Pictify |
| --- | --- | --- |
| Vendor | Photoroom | Pictify.io |
| Hosted endpoint | `https://image-api.photoroom.com/v2` | `https://api.pictify.io` |
| Transports | HTTP, Streamable HTTP | HTTP, stdio, Streamable HTTP |
| Licence | Proprietary service under the Photoroom Terms and Conditions. The sample code repository is MIT | MIT for the MCP server. The Pictify API is a closed service under terms last updated 18 July 2024 |
| Tools exposed | 1 | 25 |
| MCP registry | not listed | `io.github.pictify-io/mcp` |
| Last release | 2026-04-21 | 2026-09-20 |
| Terms last updated | 2026-07-29 | 2024-07-18 |
| Privacy policy last updated | 2026-03-01 | 2024-07-18 |
| 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 |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | none | 55 npm/wk |

Why the edge:
- Maintenance & community, Pictify +55: 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).); Pictify 68 (@pictify/mcp-server 2.0.0 published on 20 September 2026, 47 days before this check, with the changelog's newest entry dated September 2026 (20). Since 8 August, MCP versions 1.5.0 (8 August), 1.5.1 (11 August) and 2.0.0 (20 September), and changelog entries for August and September (20). GitHub issues weren't read, and the repository has one committer (5 of 25, unchecked). io.github.pictify-io/mcp is in the official MCP registry under the GitHub-verified namespace at 2.0.0, and official SDKs exist in four languages (15). CI builds and runs tests on push and pull requests (8 of 10). 20 + 20 + 5 + 15 + 8 = 68.)
- Transparency & trust, Photoroom API +17: 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).); Pictify 52 (The MCP server is MIT. The service is closed under terms of 18 July 2024 that name only Pictify.io (20 of 30). The privacy policy of the same date keeps data 'for as long as necessary' with no periods, names no processors and doesn't mention that the MCP server sends tool arguments, results and the account email to PostHog (6 of 30). The changelog records retirements, Workflows in September 2026 and MCP tools on 19 September, with no notice period or deprecation policy (5 of 20). MCP analytics are on by default and disclosed with an opt-out in the README only, and no subprocessors or data locations are listed (8 of 20). 20 + 6 + 5 + 8 = 39.)
- Agent ergonomics, Pictify +10: 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).); Pictify 74 (25 MCP tools in the 2.0.0 source (15 for 11 to 30), with no toolsets or read-only subset (15). List endpoints page with `page` and `limit` (16 of 20). Error bodies carry `code` slugs such as `quota_exceeded`, `template_limit_reached` and `invalid_variable`, and the docs say which are retryable (18 of 20). Generation is safe to retry and failed calls bill nothing, but the MCP source sets no readOnlyHint or destructiveHint, and the delete tools for templates and video templates run without a confirmation step (10 of 20). Official SDKs for Node.js, Python, Go and Ruby, sensible defaults such as 1200 x 630 PNG (15). 15 + 16 + 18 + 10 + 15 = 74.)