Adobe Photoshop API vs DynaPictures

Adobe Photoshop API 42

Adobe publishes no dated release notes, so we used the public spec. New v2 capabilities (layer effects, nested group export) were merged on 2026-09-08 and remove background was restored to the spec on 2026-09-21 (30). No releases or dated changelog entries in the last 90 days, only docs commits (5). Support goes through an Adobe customer success manager. The docs repo is active but has no public changelog (5). The official JavaScript SDK was last tagged on 2025-06-24 and targets v1 only (0). The SDK repo has CI workflows but no commits since June 2025 (2).

DynaPictures 4

No changelog, release notes or dated API change was found, and the MCP server card gives version 1.0.0 with no date (0). No dated changes since 8 August (0). Support by email and contact form, not tested (4 of 15). Not in the official MCP registry and no API SDKs (0). No public package or repository (0). 0 + 0 + 4 + 0 + 0 = 4.

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. We didn't check certifications for Firefly Services in this run (17).

DynaPictures 26

One API key per user with the user's full access, not limited to workspaces or actions; a new key is requested by email to support, with no rotation in the account (10 of 30). No read-only mode, and the MCP server can author and change designs (3 of 20). Tools return the account's own templates and renders; image layers accept outside URLs (10 of 15). A list of generated images, with no audit log documented (3 of 15). No security.txt, disclosure policy, bug bounty or certification found (0). 10 + 3 + 10 + 3 + 0 = 26.

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 (0). No free tier (0). A person has to negotiate a contract before any credentials exist (0).

DynaPictures 30

No x402, MPP or L402 (0). Image allowances per plan and AI credit packs ($20 for 1,000 credits) are public, but plan prices are filled in by the FastSpring script and weren't readable (10 of 20). Free plan and a 14-day trial with 30 API credits, no card (20). auth.md says a person has to copy the key; there is no OAuth or programmatic key (0). 0 + 10 + 20 + 0 = 30.

Adobe Photoshop API 55

status.adobe.com exists but renders only with JavaScript, so we couldn't confirm a Firefly Services or Photoshop component (10) or read its history (5). Per-organisation limits documented, 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). The usage notes say to read retry-after on 429, retry only 5xx, back off exponentially over three attempts, and that the service itself retries 429, 502, 503 and 504 three times (15). No SLA. A benchmarking page says its figures are 'not a performance SLA' (0). v2 is GA (10).

DynaPictures 42

Hosted lines. No status page found in the docs, llms.txt or footer (0). No readable incident history (5). The monthly image quota is reported in RateLimit headers on generation, but no per-second or per-minute limit is published (5 of 15). The agent skill gives a status table with what to do for each, GET /links sends Retry-After on 503, and the docs warn that generation isn't idempotent and to check before retrying a 504 (12 of 15). The terms guarantee 94 per cent annual availability, a low figure but a published SLA (10). Nothing is labelled beta (10). 0 + 5 + 5 + 12 + 10 + 10 = 42.

Adobe Photoshop API 70

OpenAPI 3.0.1 spec for v2 in the public AdobeDocs/ffs-photoshop-API repo, 8 operations (25). No llms.txt found, but the docs include a Markdown 'LLM migration reference guide' written for AI assistants (5). Five of the eight operations have a summary and no description in the spec, though the guides are long and specific (12). 94 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, but the release notes page is a heading with no entries (5).

DynaPictures 82

OpenAPI 3.1 at dynapictures.com/openapi.json with 20 paths (25). llms.txt, auth.md and an agent skill in Markdown (10). llms.txt says when to use the product and when it's a poor fit, and the skill gives call order for each job (17 of 20). Enums for formats and options, with layer overrides keyed by layer name (12 of 15). Request examples throughout and a status table in the skill, but the API reference's Errors section is unedited Slate template text about kittens (9 of 15). No URL version, additive changes, removals announced six months ahead with Deprecation and Sunset headers, and no changelog (9 of 15). 25 + 10 + 17 + 12 + 9 + 9 = 82.

Adobe Photoshop API 36

Every call returns a job and outputs go to your own storage, so responses stay small, but a full document manifest can be large (12). Little to page or filter beyond manifest options (8). Error codes defined, with Adobe's own caveat about unhelpful messages (8). No idempotency key. Retry guidance limits retries to 5xx and the status GET is safe to poll (8). The only official SDK, @adobe/photoshop-apis 2.0.1, calls only v1 /pie/psdService paths, which reached end of life on 2026-07-31, and every call needs a token exchange, two headers and pre-signed URLs (0).

DynaPictures 45

The MCP tool definitions weren't read (listing them needs a session), and llms.txt describes groups that include layer-by-layer design authoring, so the count is unknown. REST responses are small objects with image URLs (12 of 25). Template and generated-image listings, with no field selection documented (10 of 20). Errors are JSON with a message and documented statuses, without codes (12 of 20). Requests aren't idempotent, by the vendor's own note, though identical image URLs are served from cache without a credit (6 of 20). An Editor SDK for embedding the editor, and no API client SDKs (5 of 15). 12 + 10 + 12 + 6 + 5 = 45.