# Pictify vs Placid API + MCP (slim)

> Pictify scores 55.7 (C) to Placid's 43 (E) for design rendering. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/pictify-vs-placid.md (~4,550 tokens) · this version ~2,630 tokens · JSON https://www.anchorterminal.com/compare/pictify-vs-placid.json · canonical https://www.anchorterminal.com/compare/pictify-vs-placid
- 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 Placid API + MCP's 43 (E), and leads in 5 of 7 scored categories. Placid API + MCP leads on reliability and transparency & trust. Both do design rendering.

- Pictify: C 55.7, rank #856 of 1486 · https://www.anchorterminal.com/tools/pictify.min.md
- Placid API + MCP: E 43, rank #1244 of 1486 · https://www.anchorterminal.com/tools/placid.min.md
- 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 Schema & documentation, 88 against 34; Agent ergonomics, 74 against 40; Security & auth, 45 against 34; Payments & pricing, 40 against 35; Maintenance & community, 68 against 7. Also Runs on your own machine; Free to start without a card.
- Placid API + MCP, good 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 45; Transparency & trust, 58 against 52. Also No incidents deducted, where Pictify loses 3 points for them.

| Category | Pictify | Placid API + MCP |
| --- | --- | --- |
| Reliability (16%) | 45 | 75 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 88 | 34 |
| Agent ergonomics (13%) | 74 | 40 |
| Security & auth (14%) | 45 | 34 |
| Payments & pricing (10%) | 40 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 68 | 7 |
| Transparency & trust (7%) | 52 | 58 |

| Fact (where they differ) | Pictify | Placid API + MCP |
| --- | --- | --- |
| Vendor | Pictify.io | Placid |
| Hosted endpoint | `https://api.pictify.io` | `https://api.placid.app/api/rest` |
| Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Paid |
| Price for design rendering | $0.005 per image | not published |
| Licence | MIT for the MCP server. The Pictify API is a closed service under terms last updated 18 July 2024 | none |
| Tools exposed | 25 | none |
| llms.txt | yes | no |
| MCP registry | `io.github.pictify-io/mcp` | not listed |
| Last release | 2026-09-20 | none |
| Terms last updated | 2024-07-18 | 2024-11-25 |
| Privacy policy last updated | 2024-07-18 | 2024-11-18 |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | 55 npm/wk | none |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Maintenance & community, Pictify +61: 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.); Placid API + MCP 7 (We found no dated release or API change. The Headway changelog has no dates, its entries mention Integromat and a v2.0 launch, and /changelog on placid.app returns 404 (0). No dated entries in the last 90 days (0). Support by email named in the error docs, public changelog stale (4). Official PHP and Laravel libraries were last tagged v1.0.1 on 2022-07-20 and still call placid.app/api/rest (3). No CI on either library (0).)
- Schema & documentation, Pictify +54: 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.); Placid API + MCP 34 (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, and an error page with six codes but no body format (9). Docs are versioned 2.0, but the changelog on Headway carries no dates and its newest entries predate the MCP server (5).)
- Agent ergonomics, Pictify +34: 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.); Placid API + MCP 40 (Image, PDF and video objects are small and the MCP can be limited to chosen templates and creative types (15). We found no pagination or filter parameters on the pages we read (5). Six status codes documented without an error body format (10). No idempotency key, no MCP tool annotations we could see, and DELETE removes an image for good. Polling the polling_url is safe (3). Only template_uuid is required, but the official libraries are PHP and Laravel only, both last tagged v1.0.1 on 2022-07-20 (7).)
- Reliability, Placid API + MCP +30: 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.); Placid API + MCP 75 (Hyperping status page at status.placid.app with separate App and API components and 90-day bars (20). No incidents are posted. The page's own figure for the API is 99.963 per cent over 90 days, roughly 48 minutes of recorded downtime with no write-up, so minor rather than clean (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 found on the pricing page or in the docs (0). REST API 2.0 is GA (10).)
- Security & auth, Pictify +11: Pictify 45 (Prefixed API keys that can be rotated or revoked at once in the dashboard, with no scopes. The hosted MCP endpoint's metadata names api.pictify.io as authorisation server with one `mcp:tools` scope, not described in the docs (22 of 30). No read-only key or mode, and delete tools need no confirmation (5 of 20). The URL screenshot and render tools return images and URLs rather than page text, and an SSRF protection page documents how fetches are limited (10 of 15). A dashboard usage view and webhook events for renders, with no per-call audit log (5 of 15). No security.txt, disclosure policy, bug bounty or certification found; docs pages on key handling and SSRF only (3 of 20). 22 + 5 + 10 + 5 + 3 = 45.); Placid API + MCP 34 (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). A dashboard activity log is mentioned in the changelog, nothing per call documented (5). No security.txt (404), no certification in the privacy policy and no disclosure policy found (0).)
- Transparency & trust, Placid API + MCP +6: 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.); Placid API + MCP 58 (Closed service under published terms, per the 30 September check (15). Privacy policy updated 18 November 2024, a DPA on request, and raw request data kept 'for a limited amount of time' with no period stated (12). No deprecation policy or dated notices. The old changelog says v1 remains functional (3). Subprocessor categories only, with 'We don't publish further details of our data processors', and no hosting location (3).)