Head to head · Design templates · October 2026 research run

Creatomate vs Pictify

Pictify scores 55.7 (C) on agent readiness against Creatomate's 49.6 (D), and leads in 5 of 7 scored categories. Both do design templates.

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

Which one, for what

Creatomate D

Best for Teams that render video, images and GIFs from templates or JSON and want an agent to draft templates and start renders through MCP.

Also in its favour

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

Watch for

No status page, incident history or SLA found. status.creatomate.com does not resolve

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

  • Reliability, 45 against 40
  • Schema & documentation, 88 against 53
  • Agent ergonomics, 74 against 67
  • Payments & pricing, 40 against 35
  • Maintenance & community, 68 against 54

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.

Schema & documentation Pictify +35

Creatomate 53

No OpenAPI file linked from the docs or llms.txt (0); the 8 October check of a guessed path on the API host is struck as a request to the product's API. The MCP tool schemas can't be read without an account. llms.txt with 50 Markdown topic links (10). Reference and topic pages state purpose and when to use dry_run, templates or raw RenderScript, with an out-of-scope page (16). Render options are typed with ranges and status is an enum, but modifications and source are open objects, and unknown names are ignored without an error (9). Examples in nine languages and a documented error body for 400, 401, 402, 404, 429 and 500 (13). /v1 and /v2 paths, no changelog (5). 0+10+16+9+13+5 = 53.

Pictify 88

Public OpenAPI 3.1 at docs.pictify.io/openapi/v1.yaml with 20 paths (25). llms.txt on the site and docs, with a Markdown copy of every docs page and a machine-readable pricing.md (10). Endpoint pages say what each call is for, and pictify_create_image says to pass only one of html, url or template. The MCP docs page still lists 26 tools including some removed on 19 September 2026 (14 of 20). Width and height ranges (1 to 4,000), output enums and quality bounds (12 of 15). An error page with status codes, stable code slugs and what to do for each, plus examples on every endpoint page (14 of 15). Versioned v1 contract and a public changelog by month; the September 2026 entry has no day (13 of 15). 25 + 10 + 14 + 12 + 14 + 13 = 88.

Maintenance & community Pictify +14

Creatomate 54

No changelog. Dated releases since 6 August are the n8n node 0.2.0 (11 August, per the 8 October npm reading), the rebuilt n8n node v1.0.0 (11 September) and v1.0.1 (19 September, a category metadata fix, half), and @creatomate/preview 1.6.1 (3 September, removing a dependency and type definitions from the build, half). The newest release that changes code is n8n v1.0.0, 54 days before the check (20). Three counted entries in 90 days (20, cause evidence; it drops to 0 after 9 November when 0.2.0 leaves the window). Support by email, no public changelog or forum found, and two open GitHub issues across the libraries per the 8 October check (5). The Node library was last tagged 1.2.1 on 23 September 2024 and calls /v1, the PHP library was last pushed on 21 October 2024, and the Preview SDK is current (7). No CI in the Node repository (2). 20+20+5+7+2 = 54.

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.

Agent ergonomics Pictify +7

Creatomate 67

Eight MCP tools on the vendor's list, re-read on 4 November, definitions unseen, and the template list omits sources (22). A tags filter on the template list, with no pagination, limit or render list found (6). The API reference documents a hint and a documentation URL on 400, 401, 404 and 429, a hint on 402 and 500, plus advisory errors and warnings and a free dry_run (20). No idempotency key. dry_run and status polling are safe, and template delete is now described as a soft delete that an open editor can restore; MCP annotations were not readable (8). template_id alone starts a render, and the Node and PHP libraries are official but last published in 2024 (11). 22+6+20+8+11 = 67.

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.

Reliability Pictify +5

Creatomate 40

Hosted lines. No status page found. status.creatomate.com still has no DNS record and no page we read links to one (0). No readable incident history (5). 30 requests per 10 seconds per account, documented in the API reference for agents (15). The same page documents X-RateLimit-* headers on every response and Retry-After on 429 with "wait that long, do not retry immediately", but no idempotency key for renders, which are writes (10). The 8 October first-hand header reading came from a request to the product's API and is struck; the docs carry the same facts. No SLA found (0). The REST API and MCP server carry no beta label (10). 0+5+15+10+0+10 = 40.

Pictify 45

Hosted lines, for the REST API. The home page links a status page at status.pictify.io, but its robots.txt disallows every path, so its components and history weren't read. Half for a page that exists (10 of 20) and no readable history (5). Monthly render quotas are published per plan, and the docs say a few endpoints carry fixed per-minute limits without giving the numbers (5 of 15). Retry guidance is explicit. A 429 is told apart by code, rate-limit 429s send x-ratelimit-* and retry-after, a 5xx can be retried once, and generation is idempotent from the caller's side with failed requests unbilled (15). No SLA found (0). The API isn't labelled beta (10). 10 + 5 + 5 + 15 + 0 + 10 = 45.

Payments & pricing Pictify +5

Creatomate 35

No x402, MPP or L402 (0). The pricing page now shows its plan prices in the page (Essential $540 a year for 2,000 credits a month, Growth from $1,290 a year for 10,000, Beyond from $3,290 a year for 50,000), the docs give $54 and $129 for the monthly Essential and Growth 10K, and the credit formula per image and per video is public. Credits come only inside monthly plans, with no per-credit price or top-up, so this sits between plan-only and per-unit pricing, as bannerbear, placid and templated are read (15, the earlier partial kept, see open questions). A free plan with 50 credits, no card and no time limit (20). A person signs up in a browser and copies a key or signs in through OAuth (0). 0+15+20+0 = 35.

Pictify 40

No x402, MPP or L402 (0). Overage prices per render published without login, $0.02 on Basic, $0.01 on Pro and $0.005 on Business, with plan prices (20). Free plan of 50 renders a month, marked no card and no watermark (20). A person signs up and creates the key in the dashboard (0). 0 + 20 + 20 + 0 = 40.

Score by category

CategoryWeight this runCreatomatePictifyEdge
Reliability16%204045Pictify +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.25388Pictify +35
Agent ergonomics13%16.26774Pictify +7
Security & auth14%17.54845Creatomate +3
Payments & pricing10%12.53540Pictify +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85468Pictify +14
Transparency & trust7%8.85252even
Negative events≤150-3
TotalD 49.6/100C 55.7/100

Facts side by side

FactCreatomatePictify
KindHTTP APIHTTP API
VendorCreatomatePictify.io
Hosted endpointhttps://api.creatomate.com/v2https://api.pictify.io
TransportsHTTP, Streamable HTTPHTTP, stdio, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under Creatomate's Terms and Conditions. The Node, PHP and Preview SDK libraries on GitHub are MITMIT for the MCP server. The Pictify API is a closed service under terms last updated 18 July 2024
Tools exposed825
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedio.github.pictify-io/mcp
Last release2026-09-192026-09-20
Terms last updated2022-06-272024-07-18
Privacy policy last updated2022-06-272024-07-18
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot 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 waivernot found in the textnot found in the text
Popularity9 stars, 13k npm/wk55 npm/wk
Agent reviews3.3/5 (4)none

How the scores have moved

Verdicts

Creatomate

A hosted MCP server with eight tools and OAuth with PKCE sits beside a small REST API whose errors carry a hint and a documentation link, a documented rate limit with Retry-After, and a free dry_run. No status page, changelog, OpenAPI file or security contact was found, and the terms and privacy policy date from June 2022.

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

Creatomate

  1. Send "dry_run": true to POST /v2/renders before a paid render. It returns valid, errors, warnings and the effective source
  2. Read warnings on every render response. A modification keyed to an unknown element or property name is ignored without an error
  3. Keep under 30 requests per 10 seconds across the whole account, and wait for Retry-After on a 429
  4. Download each file when the webhook fires. Renders, their URLs and their status records are deleted after 30 days
  5. Use render_scale 0.5 for draft videos, about a quarter of the credits, and remember MCP create_render spends credits without a confirmation step from the server

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, Creatomate or Pictify?

Pictify scores 55.7 (C) on agent readiness against Creatomate's 49.6 (D), and leads in 5 of 7 scored categories.

Do Creatomate and Pictify need an API key?

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

Can an agent call Creatomate and Pictify without installing anything?

Yes. Creatomate has a hosted endpoint at https://api.creatomate.com/v2 and Pictify at https://api.pictify.io.

Other comparisons with Creatomate 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.