# Pictify vs Pixelixe (slim)

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

- Full: https://www.anchorterminal.com/compare/pictify-vs-pixelixe.md (~4,350 tokens) · this version ~2,430 tokens · JSON https://www.anchorterminal.com/compare/pictify-vs-pixelixe.json · canonical https://www.anchorterminal.com/compare/pictify-vs-pixelixe
- 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 Pixelixe's 37.3 (F), and leads in every scored category. Both do design rendering.

- Pictify: C 55.7, rank #861 of 1510 · https://www.anchorterminal.com/tools/pictify.min.md
- Pixelixe: F 37.3, rank #1377 of 1510 · https://www.anchorterminal.com/tools/pixelixe.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 Reliability, 45 against 15; Schema & documentation, 88 against 66; Agent ergonomics, 74 against 49; Security & auth, 45 against 38; Payments & pricing, 40 against 30; Maintenance & community, 68 against 19; Transparency & trust, 52 against 41. Also Runs on your own machine.
- Pixelixe, good for Template fills and white-label editing for marketing and SaaS teams, with a JSON-to-graphic route for agents. Also No incidents deducted, where Pictify loses 3 points for them.

| Category | Pictify | Pixelixe |
| --- | --- | --- |
| Reliability (16%) | 45 | 15 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 88 | 66 |
| Agent ergonomics (13%) | 74 | 49 |
| Security & auth (14%) | 45 | 38 |
| Payments & pricing (10%) | 40 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 68 | 19 |
| Transparency & trust (7%) | 52 | 41 |

| Fact (where they differ) | Pictify | Pixelixe |
| --- | --- | --- |
| Vendor | Pictify.io | Pixelixe |
| Hosted endpoint | `https://api.pictify.io` | `https://studio.pixelixe.com/api` |
| Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable HTTP |
| 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 | Closed service under the Pixelixe terms of service (last modified 19 March 2026) |
| Tools exposed | 25 | 7 |
| MCP registry | `io.github.pictify-io/mcp` | `com.pixelixe/pixelixe-mcp` |
| Last release | 2026-09-20 | 2026-03-26 |
| Terms last updated | 2024-07-18 | 2026-03-19 |
| Privacy policy last updated | 2024-07-18 | 2026-04-07 |
| Terms restrict automated access | not found in the text | yes |
| Popularity | 55 npm/wk | none |

Why the edge:
- Maintenance & community, Pictify +49: 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.); Pixelixe 19 (No dated release or API change was found. The newest dated items are the MCP registry entry of 26 March 2026 and the privacy policy of 7 April 2026, more than 180 days before this check (0). No three dated changes since 8 August (0). No changelog. Support by email at inquiries@pixelixe.com, not tested (4 of 15). com.pixelixe/pixelixe-mcp is in the official MCP registry under a domain-verified namespace; there are no official SDKs (15). No public package or repository (0). 0 + 0 + 4 + 15 + 0 = 19.)
- Reliability, Pictify +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.); Pixelixe 15 (Hosted lines. No status page found on the site or in the docs (0). No readable incident history (5). No rate limit is published; the terms only forbid circumventing them (0). No 429, Retry-After or backoff guidance. Every error, a wrong key and exhausted credits included, is a 400 with a message (0). No SLA found; the terms supply the service as is (0). API v2 is current and not labelled beta (10). 0 + 5 + 0 + 0 + 0 + 10 = 15.)
- Agent ergonomics, Pictify +25: 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.); Pixelixe 49 (Seven compact MCP tools (25). Document and design-set search filters, with no pagination documented (10 of 20). All errors are 400 with free-text messages, so an agent can't branch on a code (6 of 20). No idempotency keys, and annotations couldn't be read on the closed server. The MCP tools only read and create, with nothing that deletes (5 of 20). Few required fields, but no official SDK (3 of 15). 25 + 10 + 6 + 5 + 3 = 49.)
- Schema & documentation, Pictify +22: 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.); Pixelixe 66 (OpenAPI 3.1 (version 2.0.0) at pixelixe.com/pixelixe-openapi.json, but it covers four endpoints, authentication, document search, graphic automation and photo effects, and leaves out the JSON-to-graphic and image processing APIs (18 of 25). llms.txt exists but routes readers to marketing pages; the MCP reference is written for LLMs (7 of 10). The MCP reference says what each of the seven tools maps to, that `pixelixe_generate_graphic_variant` 'is not a free-form layout API', lists common mistakes and how to present outputs (17 of 20). The MCP layer documents canonical field names and refuses legacy aliases; the REST modifications are open structures keyed by element name (10 of 15). Request examples throughout, but errors are one table of message strings all returning 400 (8 of 15). /v2 paths and a deprecated V1, with no changelog (6 of 15). 18 + 7 + 17 + 10 + 8 + 6 = 66.)
- Transparency & trust, Pictify +11: 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.); Pixelixe 41 (Closed service under terms of 19 March 2026 that choose French law but name no company (12 of 30). The privacy policy of 7 April 2026 keeps account data while the account is active and 'as long as reasonably necessary' after, with no periods, and says nothing about AI processing or training (10 of 30). V1 is marked deprecated in the docs with no dates or notice period (5 of 20). Processors are described only by category, with Google Analytics named, and data processed in France, the EEA and other vendor countries (5 of 20). 12 + 10 + 5 + 5 = 32.)
- Payments & pricing, Pictify +10: 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.); Pixelixe 30 (No x402, MPP or L402 (0). Plan prices with monthly document counts are public, with no per-image price (10). 10-day trial with no card (20). A person signs up and copies the key, or approves OAuth in a browser (0). 0 + 10 + 20 + 0 = 30.)