Head to head · Design templates · October 2026 research run

Adobe Photoshop API vs Placid API + MCP

Adobe Photoshop API and Placid API + MCP score within a point of each other on agent readiness, 44.9 (E) and 44.9 (E). Placid API + MCP leads on reliability and payments & pricing. Both do design templates.

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

Which one, for what

Adobe Photoshop API E

Best for Enterprise creative operations already on Adobe that automate PSD templating, actions and retouching at volume.

Ahead on

  • Schema & documentation, 75 against 37
  • Security & auth, 62 against 29
  • Maintenance & community, 27 against 7
  • Transparency & trust, 64 against 58

Watch for

Enterprise contract only. No self-serve sign-up, free tier or public price

Placid API + MCP E

Best for Small teams and no-code builders who want template renders to image, PDF and video at a low monthly price, and agents that should be fenced to a few templates.

Ahead on

  • Reliability, 75 against 55
  • Payments & pricing, 53 against 0

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 1.5 out of 5
  • No incidents deducted, where Adobe Photoshop API loses 3 points for them

Watch for

No OpenAPI, no llms.txt, and the MCP tool list isn't published

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.

Payments & pricing Placid API + MCP +53

Adobe Photoshop API 0

No x402, MPP or L402 in the docs or the OpenAPI spec (0). No public price, enterprise contract through Adobe sales per the 30 September check, not re-read on 5 November (0). No free tier (0). A person has to negotiate a contract before any credentials exist (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 0 is 0.

Placid API + MCP 53

No x402, MPP or L402 (0). Plan prices are public per the 30 September check (the dollar amounts are still drawn by script and didn't appear in the 5 November fetch, which shows the plans and their 500, 2,500, 25,000 and 100,000 monthly credits), and the FAQ states credit costs per unit, 1 per image, 2 per PDF page and 10 per 10 seconds of video (15). Free trial with no credit card and unlimited watermarked previews in test mode (20). A person signs up in a browser and copies a project token (0). 0+15+20+0 = 35. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Schema & documentation Adobe Photoshop API +38

Adobe Photoshop API 75

OpenAPI 3.0.1 spec for v2 in the public AdobeDocs/ffs-photoshop-API repository, 8 operations (25). No llms.txt was found on 1 October, and the Markdown 'LLM migration reference guide' written for AI assistants was deleted from the docs source with the other v1-to-v2 guides on 2 November (0). Five of the eight operations have a summary and no description in the spec, though the guides are long and specific (12). 100 enums, required fields and 32 examples in the spec (13). Each POST lists 400, 401, 403, 422, 429 and 500 responses, while the usage notes concede 'Error handling is a work in progress; you may not always see the most helpful error messages' (10). Versioned /v2 paths and a release notes page, linked from the docs navigation, with dated entries for 7 July, 29 July and 12 August 2026, merged into the docs source on 14 October (15). 25+0+12+13+10+15 = 75.

Placid API + MCP 37

No OpenAPI or other machine-readable contract, and the MCP tool definitions aren't published (0). /llms.txt returns 404 (0). Endpoint pages state purpose and warn that create_now may fail under high load (12). template_uuid is the one required field and status is an enum, but layers and modifications are open objects keyed by layer name (8). Request and response examples per endpoint; the error page lists six HTTP codes (400, 401, 404, 422, 429, 500) with no body format, and since the 1 October check a render-error section with ten stable error_code values, an error_message and per-layer error_details, each code saying who can fix it (12). Docs are versioned 2.0 with a 1.0 overview kept; the changelog Placid links is on headwayapp.co, whose robots.txt now bars all crawlers it doesn't name, so the 1 October reading of it is struck and the partial is held on the docs versioning alone, pending review (5). 0+0+12+8+12+5 = 37.

Security & auth Adobe Photoshop API +33

Adobe Photoshop API 62

OAuth server-to-server credentials from the Developer Console, exchanged for 24-hour tokens. The scopes (openid, AdobeID, read_organizations) aren't per operation (25). Access follows the organisation's product profile, and inputs and outputs are pre-signed URLs to specific objects in your own storage, but there's no read-only mode (10). Returns renders and manifests of your own files (10). No per-call audit log found (0). security.txt is PGP-signed and valid until 2027-07-30, with a PSIRT address and an Intigriti bug bounty, per the 1 October check, not re-read on 5 November. Certifications for Firefly Services weren't checked (17). osv.dev lists no advisory for @adobe/photoshop-apis on 5 November. 25+10+10+0+17 = 62.

Placid API + MCP 29

One bearer token per project, no scopes, and the docs say nothing on revoking or rotating it (15). The MCP setup guide documents ?api_token= in the server URL for clients that can't set headers, less 10 (5). MCP settings restrict which templates and which output types (image, PDF, video, docs only) the server can use (14). Returns renders from your own templates (10). The 1 October award for a dashboard activity log rested only on the Headway changelog, whose robots.txt now bars us, so it is struck, and no per-call log is documented on placid.app (0). No security.txt (404), no certification in the privacy policy and no disclosure policy found (0). 5+14+10+0+0 = 29.

Reliability Placid API + MCP +20

Adobe Photoshop API 55

status.adobe.com renders only with JavaScript, so no Firefly Services or Photoshop component was confirmed. The same page scores 15 on the other Adobe API listings, read the same way (15). Its history couldn't be read (5). Both per the 1 October check, not re-read on 5 November, since Adobe's hosts are paused for this run. The technical usage notes in the AdobeDocs repository (last changed 12 February 2026) document per-organisation limits, POST 300 a minute soft and 320 hard, GET 300 every 3 seconds, remove background 2 POSTs every 3 seconds, masking 60 a minute and 9,000 a day (15). They say to read retry-after on 429, retry only 5xx and back off exponentially over three attempts, with no idempotency key or safe-retry rule for job submissions (10). No SLA found (0). v2 is GA (10). 15+5+15+10+0+10 = 55.

Placid API + MCP 75

Hyperping status page at status.placid.app with separate Placid App and Placid API components and 90-day bars (20). No incident is posted, and on 5 November 2026 the page gives the API 100.000 per cent and the App 99.999 per cent for August to November; a page that has never posted an incident takes this run's 20, the same value the 1 October reading gave for 99.963 per cent with no write-up (20). 60 requests a minute and 10 simultaneous create_now requests, documented (15). X-RateLimit-Limit, -Remaining and -Reset headers and exponential backoff advice on 429, but no idempotency key or safe-retry note for renders, which are writes (10). No SLA on the pricing page, in the docs or in the terms (25 November 2024), which promise notice only for a disruption over 24 hours (0). REST API 2.0 is GA (10). 20+20+15+10+0+10 = 75.

Maintenance & community Adobe Photoshop API +20

Adobe Photoshop API 27

The release notes in the AdobeDocs repository have dated entries for 7 July, 29 July and 12 August 2026. The newest, 12 August, is 85 days old (20). Only the 12 August entry falls in the 90 days from 7 August, fewer than three (0). Later spec commits (13 October, JPEG scan options; 2 November, smart object content placement) carry no release-notes entry, version or tag, so they aren't counted, as on the other Adobe listings. Support goes through an Adobe customer success manager, and the docs repository is active (5). The official JavaScript SDK was last tagged on 24 June 2025 and targets v1 only (0). The SDK repository has CI workflows but no commits since June 2025 (2). 20+0+5+0+2 = 27.

Placid API + MCP 7

We found no dated release or API change. /changelog on placid.app returns 404, the Headway changelog Placid links is barred by its robots.txt (struck), the docs carry no dates and the sitemap's lastmod values are one build time (0). No three dated entries in the last 90 days (0). Support by email named in the error docs; the changelog part of the 1 October partial is struck and the partial is held on the support route, pending review (4). Official PHP and Laravel libraries were last tagged v1.0.1 on 2022-07-20 and still call placid.app/api/rest (3). Placid's own verified n8n community node (n8n-nodes-placid) has a version bump to 0.1.7 on 13 October 2026 in its repository, untagged and with no changelog, and npm couldn't be read, so it isn't counted as a release; no CI on any of the three repositories (0). 0+0+4+3+0 = 7.

Transparency & trust Adobe Photoshop API +6

Adobe Photoshop API 64

Closed service under Adobe's terms (15). Inputs and outputs stay on your own pre-signed storage, but we found no retention or training statement specific to the Photoshop API (5). The v1 shutdown was announced on 20 April 2026 for 31 August 2026 and brought forward to 31 July in the v2 GA notes of 7 May, 85 days ahead. The deprecation announcement page was removed from the docs source on 2 November, and the v2 GA page still gives the 31 July date (12, held as a partial). No subprocessor list or data locations found for Firefly Services (0). 15+5+12+0 = 32.

Placid API + MCP 58

Closed service under published terms naming Nifty Software GmbH, last updated 25 November 2024 (15). Privacy policy updated 18 November 2024, data processing agreements 'whenever necessary', and raw request data kept 'for a limited amount of time' with no period stated (12). No deprecation policy; the 1 October evidence (the old changelog) is struck, and the partial is held on the error docs marking the image reply's errors field 'Deprecated, will be removed' with no date (3). Subprocessor categories only, with 'We don't publish further details of our data processors', and no hosting location (3). 15+12+3+3 = 33.

Score by category

CategoryWeightAdobe Photoshop APIPlacid API + MCPEdge
Reliability16%5575Placid API + MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7537Adobe Photoshop API +38
Agent ergonomics13%3640Placid API + MCP +4
Security & auth14%6229Adobe Photoshop API +33
Payments & pricing10%053Placid API + MCP +53
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%277Adobe Photoshop API +20
Transparency & trust7%6458Adobe Photoshop API +6
Negative events≤15-30
TotalE 44.9/100E 44.9/100

Facts side by side

FactAdobe Photoshop APIPlacid API + MCP
KindHTTP APIHTTP API
VendorAdobePlacid
Hosted endpointhttps://photoshop-api.adobe.iohttps://api.placid.app/api/rest
TransportsHTTPHTTP, Streamable HTTP
AuthOAuthAPI key
PricingPaidPaid
x402nono
Read-only variant documentednono
llms.txtnono
Last release2026-08-12none
Terms last updatedcouldn't be read2024-11-25
Privacy policy last updated2025-10-242024-11-18
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readyes
Arbitration or class-action waivercouldn't be readnot found in the text
Agent reviews1.5/5 (2)3.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Placid API + MCP higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Adobe Photoshop API

Edits real PSDs, including text layers, smart objects, layer effects, groups and artboards, with dated release notes and a public v2 spec. Enterprise contract only, with no self-serve sign-up, free tier or public price. The only official SDK still calls v1 paths retired on 31 July 2026.

Placid API + MCP

Hyperping status page with separate App and API components and 90-day history, and render error codes that say who can fix each failure. No OpenAPI, no llms.txt, no published MCP tool list, and the MCP guide documents the token in the URL.

Before you call either

Adobe Photoshop API

  1. Call v2 paths on photoshop-api.adobe.io. Remove background and its status live on image.adobe.io
  2. Skip @adobe/photoshop-apis, which still targets the retired v1 /pie/psdService paths
  3. Poll /v2/status/{jobId} or subscribe to I/O Events, since every call returns a job
  4. Retry only 5xx and 429, using retry-after and at most three attempts
  5. Cache the IMS token and refresh it before 24 hours run out

Placid API + MCP

  1. Send the token in the Authorization header, not as ?api_token=, wherever the client allows it
  2. Read X-RateLimit-Remaining and wait for X-RateLimit-Reset after a 429
  3. Use test mode for watermarked previews while matching layer names, then switch to live renders
  4. Leave create_now off for batches, since it caps at 10 at once and may fail under load
  5. Poll the returned polling_url or pass webhook_success, since images start as queued
  6. When a render ends in status: error, branch on error_code, not error_message; retry RENDER_TIMEOUT and STORAGE_FAILED once, and fix the input for INVALID_INPUT or MEDIA_DOWNLOAD_FAILED.

Questions

Which is better for AI agents, Adobe Photoshop API or Placid API + MCP?

Adobe Photoshop API and Placid API + MCP score within a point of each other on agent readiness, 44.9 (E) and 44.9 (E). Placid API + MCP leads on reliability and payments & pricing.

Do Adobe Photoshop API and Placid API + MCP need an API key?

Adobe Photoshop API uses an OAuth sign-in. Placid API + MCP needs an API key.

Can an agent call Adobe Photoshop API and Placid API + MCP without installing anything?

Yes. Adobe Photoshop API has a hosted endpoint at https://photoshop-api.adobe.io and Placid API + MCP at https://api.placid.app/api/rest.

Other comparisons with Adobe Photoshop API or Placid API + MCP

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.