Head to head · Design templates · October 2026 research run

Photoroom API vs Pictify

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.

Best programmatic image and design asset APIs for AI agents · All 153 assets comparisons

Which one, for what

Photoroom API D

Best 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 in its favour

  • No incidents deducted, where Pictify loses 3 points for them

Watch for

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

Pictify C

Best 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 in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

The MCP server sends tool arguments, results and the account email to PostHog unless turned off

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

Score by category

CategoryWeight this runPhotoroom APIPictifyEdge
Reliability16%204245Pictify +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28688Pictify +2
Agent ergonomics13%16.26474Pictify +10
Security & auth14%17.54945Photoroom API +4
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.81368Pictify +55
Transparency & trust7%8.86952Photoroom API +17
Negative events≤150-3
TotalD 53.5/100C 55.7/100

Facts side by side

FactPhotoroom APIPictify
KindHTTP APIHTTP API
VendorPhotoroomPictify.io
Hosted endpointhttps://image-api.photoroom.com/v2https://api.pictify.io
TransportsHTTP, Streamable HTTPHTTP, stdio, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceProprietary service under the Photoroom Terms and Conditions. The sample code repository is MITMIT for the MCP server. The Pictify API is a closed service under terms last updated 18 July 2024
Tools exposed125
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.pictify-io/mcp
Last release2026-04-212026-09-20
Terms last updated2026-07-292024-07-18
Privacy policy last updated2026-03-012024-07-18
Customer content may train modelsyes, with an opt-outnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularitynone55 npm/wk

How the scores have moved

Verdicts

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.

Pictify

A public OpenAPI 3.1 contract, per-render overage prices, a recurring no-card free tier and error codes that tell quota apart from rate limits make Pictify easy for an agent to call and budget. Its MCP server reports tool arguments and results to PostHog by default, and the privacy policy, last updated July 2024, mentions neither.

Before you call either

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

Pictify

  1. Set PICTIFY_ANALYTICS_DISABLED=1 in the MCP server's env when tool inputs are confidential
  2. On a 429, read code first; quota_exceeded means wait for the monthly reset, not retry
  3. Retry a 5xx once; a failed generation bills nothing
  4. Pass only one of html, url or template to pictify_create_image
  5. Use batch render for one image per row rather than many single calls

Questions

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

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.

Do Photoroom API and Pictify need an API key?

Both take an API key or an OAuth sign-in.

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

Yes. Photoroom API has a hosted endpoint at https://image-api.photoroom.com/v2 and Pictify at https://api.pictify.io.

Other comparisons with Photoroom API or Pictify

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.