{ "data": { "a": { "slug": "pictify", "name": "Pictify", "vendor": "Pictify.io", "vendorUrl": "https://pictify.io", "kind": "http-api", "category": "design-assets", "summary": "Pictify renders HTML, URLs and saved templates into PNG, JPG or WebP images, PDFs, GIFs and MP4 video through a REST API, official SDKs in four languages and an MCP server.", "url": "https://www.anchorterminal.com/tools/pictify", "markdownUrl": "https://www.anchorterminal.com/tools/pictify.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/pictify.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/pictify.json", "dns": "pictify.grade.anchorterminal.com", "repo": "https://github.com/pictify-io/mcp", "license": "MIT for the MCP server. The Pictify API is a closed service under terms last updated 18 July 2024", "transports": [ "http", "stdio", "streamable-http" ], "remoteUrl": "https://api.pictify.io", "packages": [ { "registry": "npm", "name": "@pictify/mcp-server" } ], "auth": "mixed", "authNotes": "API keys (`pic_live_` plus 64 hex characters since September 2026) created in the dashboard and sent as `Authorization: Bearer`. Keys can be rotated (a replacement is made, then the old key revoked) or revoked at once. No scopes. The local MCP server reads `PICTIFY_API_KEY`; a hosted MCP endpoint at mcp.pictify.io advertises OAuth with an `mcp:tools` scope, which the docs don't describe.", "pricing": "freemium", "pricingNotes": "Free $0 with 50 renders a month, 3 saved templates and no card. Basic $19 a month ($15 yearly) with 1,000 renders and $0.02 per extra render, Pro $49 ($39) with 10,000 and $0.01, Business $249 ($199) with 40,000 and $0.005. One render pool covers images, PDF pages, GIFs and video. Failed requests aren't billed.", "priceSummary": "Freemium", "where": "both", "x402": { "level": "no", "evidence": "Subscriptions with overage billing. No x402, MPP or L402 in the OpenAPI, the docs, llms.txt or pricing.md (checked 2026-11-06). Exhausted credits return 429 or 402 with `quota_exceeded` and no payment requirements.", "endpoints": [] }, "toolCount": 25, "popularity": { "githubStars": null, "npmWeekly": 55, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://docs.pictify.io", "llmsTxt": "https://docs.pictify.io/llms.txt", "openapi": "https://docs.pictify.io/openapi/v1.yaml", "registryName": "io.github.pictify-io/mcp", "capabilities": [ "design.render", "design.templates", "pdf.generate", "video.generate" ], "tags": [ "hosted", "openapi", "llms-txt", "mcp", "stdio", "mcp-registry", "api-key", "freemium", "free-tier", "no-card", "webhooks", "telemetry" ], "lastRelease": "2026-09-20", "graded": true, "anchor": { "graded": true, "score": 55.7, "grade": "C", "agentReady": false, "rank": 861, "ranked": true, "rankOf": 1510, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 74, "maintenance": 68, "payments": 40, "reliability": 45, "schema": 88, "security": 45, "transparency": 52 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": -3, "negativeNotes": [ "Workflows (CSV or webhook runs with per-recipient email delivery) were retired in September 2026 per the changelog (https://docs.pictify.io/resources/changelog.md), while pictify.io's llms.txt still calls the Render-to-Recipient workflow Pictify's core pattern and pricing.md (last updated 9 August 2026) still says per-recipient email delivery is included on paid workflow runs (https://pictify.io/llms.txt, https://pictify.io/pricing.md), read 6 November 2026. A retired feature still advertised, -3." ], "verdict": "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.", "bestFor": "HTML-to-image, template renders, PDFs and short video from one API, with per-render prices an agent can budget.", "strengths": [ "Public OpenAPI 3.1, llms.txt and Markdown docs, with official SDKs in Node.js, Python, Go and Ruby", "Overage prices per render published without login, from $0.02 down to $0.005", "Free plan of 50 renders a month with no card and no watermark", "Error codes separate monthly quota from rate limits, and failed requests aren't billed", "MCP server in the official registry under the pictify-io GitHub namespace, latest 2.0.0" ], "weaknesses": [ "The MCP server sends tool arguments, results and the account email to PostHog unless turned off", "Privacy policy and terms date from 18 July 2024 and name no company or processors", "Workflows were retired in September 2026 but llms.txt and pricing.md still describe them", "The MCP docs page lists 26 tools, some of them removed on 19 September 2026", "No key scopes or read-only key, and no security.txt or disclosure policy" ], "agentNotes": [ "Set `PICTIFY_ANALYTICS_DISABLED=1` in the MCP server's env when tool inputs are confidential", "On a 429, read `code` first; `quota_exceeded` means wait for the monthly reset, not retry", "Retry a 5xx once; a failed generation bills nothing", "Pass only one of `html`, `url` or `template` to `pictify_create_image`", "Use batch render for one image per row rather than many single calls" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 55.7 } ], "editorialScores": { "ergonomics": 74, "maintenance": 68, "payments": 40, "reliability": 45, "schema": 88, "security": 45, "transparency": 39 }, "provenanceScore": 64, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npx -y @pictify/mcp-server", "claudeCode": "claude mcp add pictify -- npx -y @pictify/mcp-server", "config": { "mcpServers": { "pictify": { "args": [ "-y", "@pictify/mcp-server" ], "command": "npx", "env": { "PICTIFY_API_KEY": "YOUR_API_KEY" } } } } }, "letme": { "capability": "https://letme.dev/design.render", "tool": "https://letme.dev/pictify" }, "area": "design-diagrams", "unitPrices": [ { "item": "Extra render on Basic", "unit": "image", "usd": 0.02, "note": "Basic $19 a month includes 1,000 renders; one pool for images, PDF pages, GIFs and video" }, { "item": "Extra render on Pro", "unit": "image", "usd": 0.01, "note": "Pro $49 a month includes 10,000 renders" }, { "item": "Extra render on Business", "unit": "image", "usd": 0.005, "note": "Business $249 a month includes 40,000 renders" } ], "provenance": { "legalEntity": "", "domain": "pictify.io", "domainRegistered": "2024-02-18", "endpointOnVendorDomain": true, "terms": "https://pictify.io/terms", "privacy": "https://pictify.io/privacy", "statusPage": "https://status.pictify.io", "changelog": "https://docs.pictify.io/resources/changelog", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The terms and privacy policy, both last updated 18 July 2024, name only Pictify.io and choose United States law. No company form or address is given. The npm package's maintainer is Suyash Thakur.", "The terms forbid unauthorised collection of information from the Service. Public pages were read as data.", "pictify.io/robots.txt allows all but the dashboard, login, signup, workspace, canvas, invite and /api/ paths, with Content-Signal search=yes, ai-input=yes, ai-train=yes. docs.pictify.io allows the docs. status.pictify.io/robots.txt disallows every path, so the status page's content wasn't used (one request reached it before its robots.txt was read, and what it returned was discarded).", "RDAP gives pictify.io a registration date of 18 February 2024.", "/.well-known/security.txt returns 404." ], "score": 64 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/pictify.json", "live": { "slug": "pictify", "probe": { "target": "https://api.pictify.io", "method": "get", "lastAt": "2026-11-07T19:22:26.148949772Z", "lastOk": true, "lastStatus": 404, "lastMs": 244, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 248, "p95ms24h": 416, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://status.pictify.io", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:36.108648674Z" }, "versions": [ { "registry": "mcp-registry", "name": "io.github.pictify-io/mcp", "version": "2.0.0", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "@pictify/mcp-server", "version": "2.0.0", "seenAt": "2026-11-06T23:56:03.791188542Z" } ], "githubStars": 0, "npmWeekly": 55, "securityTxt": { "url": "https://pictify.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:53.674703481Z" }, "llmsTxt": { "url": "https://docs.pictify.io/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:37.409193605Z" }, "pages": [ { "url": "https://docs.pictify.io/resources/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:07:29.763829977Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8886bf07ecff" }, { "url": "https://pictify.io/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:16:26.928025338Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "de6aaaa6113c" }, { "url": "https://pictify.io/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:16:29.17143268Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "f3dfbe385bd9" } ], "updatedAt": "2026-11-07T19:22:26.148949772Z" } }, "answer": "Pictify scores 55.7 (C) on agent readiness against Pixelixe's 37.3 (F), and leads in every scored category.", "b": { "slug": "pixelixe", "name": "Pixelixe", "vendor": "Pixelixe", "vendorUrl": "https://pixelixe.com", "kind": "http-api", "category": "design-assets", "summary": "Pixelixe is a template-based graphic platform with a design studio, an Image Automation API that fills saved templates into PNG, JPEG, PDF or HTML, a JSON-to-graphic API, image filters, a white-label editor and a remote MCP server.", "url": "https://www.anchorterminal.com/tools/pixelixe", "markdownUrl": "https://www.anchorterminal.com/tools/pixelixe.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/pixelixe.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/pixelixe.json", "dns": "pixelixe.grade.anchorterminal.com", "license": "Closed service under the Pixelixe terms of service (last modified 19 March 2026)", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://studio.pixelixe.com/api", "packages": [], "auth": "mixed", "authNotes": "REST calls send the account's API key as `Authorization: Bearer`, from the account after signup; a separate public key is for embedding the editor in a web page. The remote MCP server at studio.pixelixe.com/api/mcp/v1 takes the API key or an OAuth access token from studio.pixelixe.com/oauth/mcp, with one `pixelixe.mcp` scope. No key scopes or rotation documented.", "pricing": "paid", "pricingNotes": "API access starts with Automate at $59 a month (20,000 automated documents, 140 AI actions). Scale $119 (60,000), Enterprise from $299 (300,000 and up). Create at $12 a month has no API. 10-day trial with no card. No per-image price.", "priceSummary": "$59 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "Monthly plans. No x402, MPP or L402 in the OpenAPI, the v2 docs, the MCP docs or llms.txt (checked 2026-11-06). Exhausted credits return 400 with a message.", "endpoints": [] }, "toolCount": 7, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://pixelixe.com/docs/v2/", "llmsTxt": "https://pixelixe.com/llms.txt", "openapi": "https://pixelixe.com/pixelixe-openapi.json", "registryName": "com.pixelixe/pixelixe-mcp", "capabilities": [ "design.templates", "design.render", "image.edit", "pdf.generate" ], "tags": [ "hosted", "openapi", "llms-txt", "mcp", "remote-mcp", "mcp-registry", "oauth", "api-key", "white-label", "trial", "no-card", "eu" ], "lastRelease": "2026-03-26", "graded": true, "anchor": { "graded": true, "score": 37.3, "grade": "F", "agentReady": false, "rank": 1377, "ranked": true, "rankOf": 1510, "categoryRank": 15, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 49, "maintenance": 19, "payments": 30, "reliability": 15, "schema": 66, "security": 38, "transparency": 41 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Pixelixe's seven MCP tools and their LLM-oriented reference make template fills and JSON-to-graphic creation simple to call, with an OpenAPI file for the core endpoints. Every error comes back as a 400 with a message, there are no published rate limits, status page or changelog, and API access starts at $59 a month.", "bestFor": "Template fills and white-label editing for marketing and SaaS teams, with a JSON-to-graphic route for agents.", "strengths": [ "Seven compact MCP tools with a reference that states the canonical fields and common LLM mistakes", "OpenAPI 3.1 for the authentication, search, automation and photo effect endpoints", "Creates editable graphics from a single JSON document, returned as HTML or saved for reuse", "Remote MCP server with OAuth, in the official registry under a domain-verified namespace", "10-day trial without a card" ], "weaknesses": [ "Every error is HTTP 400 with a free-text message, including wrong keys and exhausted credits", "No rate limits, status page, SLA or changelog found", "API access starts at $59 a month; the $12 plan has none", "The OpenAPI file covers four endpoints, not the JSON-to-graphic or image processing APIs", "The terms and privacy policy name no company, and no processors are listed" ], "agentNotes": [ "Call `pixelixe_search_documents` first to find the `document_uid` of the template to reuse", "Use `pixelixe_generate_graphic_variant` to fill an existing template; it can't change the layout", "Read the error `message` text, since every failure is a 400", "Stop and tell the user on 'Not enough Credits'; retrying won't help", "For a batch, use `pixelixe_create_multiple_images` and summarise counts rather than inlining every image" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "F", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 37.3 } ], "editorialScores": { "ergonomics": 49, "maintenance": 19, "payments": 30, "reliability": 15, "schema": 66, "security": 38, "transparency": 32 }, "provenanceScore": 49, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -X POST https://studio.pixelixe.com/api/authentication/v2 -H \"Authorization: Bearer $PIXELIXE_API_KEY\"", "claudeCode": "claude mcp add --transport http pixelixe https://studio.pixelixe.com/api/mcp/v1", "config": { "mcpServers": { "pixelixe": { "url": "https://studio.pixelixe.com/api/mcp/v1" } } } }, "letme": { "capability": "https://letme.dev/design.templates", "tool": "https://letme.dev/pixelixe" }, "area": "design-diagrams", "unitPrices": [ { "item": "Automate plan", "unit": "month", "usd": 59, "note": "20,000 automated documents and 140 AI actions a month" }, { "item": "Scale plan", "unit": "month", "usd": 119, "note": "60,000 automated documents and 280 AI actions a month" } ], "provenance": { "legalEntity": "", "domain": "pixelixe.com", "domainRegistered": "2018-09-17", "endpointOnVendorDomain": true, "terms": "https://pixelixe.com/terms.html", "privacy": "https://pixelixe.com/privacy-policy.html", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The terms (last modified 19 March 2026) and privacy policy (effective 7 April 2026) name the operator only as Pixelixe and choose French law and the courts of Paris.", "The terms forbid scraping or copying the Service. Public pages were read as data.", "pixelixe.com/robots.txt allows the docs and names ClaudeBot as allowed; it disallows /studio/, /docs/v1/ and some demo pages. studio.pixelixe.com/robots.txt disallows the app pages, /assets and /js/ but not /api/ or /.well-known/.", "RDAP gives pixelixe.com a registration date of 17 September 2018.", "/.well-known/security.txt returns 404. No status page or changelog found." ], "score": 49 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/pixelixe.json", "live": { "slug": "pixelixe", "probe": { "target": "https://studio.pixelixe.com/api", "method": "get", "lastAt": "2026-11-07T19:22:26.523715438Z", "lastOk": true, "lastStatus": 404, "lastMs": 67, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 33, "p95ms24h": 121, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "versions": [ { "registry": "mcp-registry", "name": "com.pixelixe/pixelixe-mcp", "version": "1.0.2", "seenAt": "2026-11-07T18:16:28.95801333Z" } ], "securityTxt": { "url": "https://pixelixe.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:01:00.920272687Z" }, "llmsTxt": { "url": "https://pixelixe.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:38.090224197Z" }, "pages": [ { "url": "https://pixelixe.com/privacy-policy.html", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:16:29.788755256Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "832cb532d5ba" }, { "url": "https://pixelixe.com/terms.html", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:16:31.916703951Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "764ac1d560a1" } ], "mcpTools": { "url": "https://studio.pixelixe.com/api/mcp/v1", "checkedAt": "2026-11-07T01:46:51.581135972Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:51.581135972Z" }, "updatedAt": "2026-11-07T19:22:26.523715438Z" } }, "edges": [ { "by": 49, "category": "maintenance", "leads": "pictify", "name": "Maintenance \u0026 community", "reasons": { "a": "@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.", "b": "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." }, "scores": { "a": 68, "b": 19 } }, { "by": 30, "category": "reliability", "leads": "pictify", "name": "Reliability", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 45, "b": 15 } }, { "by": 25, "category": "ergonomics", "leads": "pictify", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 74, "b": 49 } }, { "by": 22, "category": "schema", "leads": "pictify", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 88, "b": 66 } }, { "by": 11, "category": "transparency", "leads": "pictify", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 52, "b": 41 } }, { "by": 10, "category": "payments", "leads": "pictify", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "b": "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." }, "scores": { "a": 40, "b": 30 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Pictify.io", "b": "Pixelixe", "name": "Vendor" }, { "a": "https://api.pictify.io", "b": "https://studio.pixelixe.com/api", "name": "Hosted endpoint" }, { "a": "HTTP, stdio, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "$0.005 per image", "b": "not published", "name": "Price for design rendering" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT for the MCP server. The Pictify API is a closed service under terms last updated 18 July 2024", "b": "Closed service under the Pixelixe terms of service (last modified 19 March 2026)", "name": "Licence" }, { "a": "25", "b": "7", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.github.pictify-io/mcp", "b": "com.pixelixe/pixelixe-mcp", "name": "MCP registry" }, { "a": "2026-09-20", "b": "2026-03-26", "name": "Last release" }, { "a": "2024-07-18", "b": "2026-03-19", "name": "Terms last updated" }, { "a": "2024-07-18", "b": "2026-04-07", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "55 npm/wk", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Pictify scores 55.7 (C) on agent readiness against Pixelixe's 37.3 (F), and leads in every scored category.", "question": "Which is better for AI agents, Pictify or Pixelixe?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Pictify and Pixelixe need an API key?" }, { "answer": "Yes. Pictify has a hosted endpoint at https://api.pictify.io and Pixelixe at https://studio.pixelixe.com/api.", "question": "Can an agent call Pictify and Pixelixe without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 45 against 15", "Schema \u0026 documentation, 88 against 66", "Agent ergonomics, 74 against 49", "Security \u0026 auth, 45 against 38", "Payments \u0026 pricing, 40 against 30", "Maintenance \u0026 community, 68 against 19", "Transparency \u0026 trust, 52 against 41" ], "also": [ "Runs on your own machine" ], "goodFor": "HTML-to-image, template renders, PDFs and short video from one API, with per-render prices an agent can budget.", "slug": "pictify", "watchFor": "The MCP server sends tool arguments, results and the account email to PostHog unless turned off" }, { "aheadOn": null, "also": [ "No incidents deducted, where Pictify loses 3 points for them" ], "goodFor": "Template fills and white-label editing for marketing and SaaS teams, with a JSON-to-graphic route for agents.", "slug": "pixelixe", "watchFor": "Every error is HTTP 400 with a free-text message, including wrong keys and exhausted credits" } ], "history": null, "job": { "capability": "design.render", "name": "Design rendering" }, "others": [ { "json": "https://www.anchorterminal.com/compare/apitemplate-io-vs-pictify.json", "title": "APITemplate.io vs Pictify", "url": "https://www.anchorterminal.com/compare/apitemplate-io-vs-pictify" }, { "json": "https://www.anchorterminal.com/compare/apitemplate-io-vs-pixelixe.json", "title": "APITemplate.io vs Pixelixe", "url": "https://www.anchorterminal.com/compare/apitemplate-io-vs-pixelixe" }, { "json": "https://www.anchorterminal.com/compare/bannerbear-vs-pictify.json", "title": "Bannerbear API + MCP vs Pictify", "url": "https://www.anchorterminal.com/compare/bannerbear-vs-pictify" }, { "json": "https://www.anchorterminal.com/compare/bannerbear-vs-pixelixe.json", "title": "Bannerbear API + MCP vs Pixelixe", "url": "https://www.anchorterminal.com/compare/bannerbear-vs-pixelixe" }, { "json": "https://www.anchorterminal.com/compare/canva-vs-pictify.json", "title": "Canva REST APIs + MCP vs Pictify", "url": "https://www.anchorterminal.com/compare/canva-vs-pictify" }, { "json": "https://www.anchorterminal.com/compare/canva-vs-pixelixe.json", "title": "Canva REST APIs + MCP vs Pixelixe", "url": "https://www.anchorterminal.com/compare/canva-vs-pixelixe" }, { "json": "https://www.anchorterminal.com/compare/contentdrips-vs-pictify.json", "title": "Contentdrips API and MCP vs Pictify", "url": "https://www.anchorterminal.com/compare/contentdrips-vs-pictify" }, { "json": "https://www.anchorterminal.com/compare/contentdrips-vs-pixelixe.json", "title": "Contentdrips API and MCP vs Pixelixe", "url": "https://www.anchorterminal.com/compare/contentdrips-vs-pixelixe" }, { "json": "https://www.anchorterminal.com/compare/creatomate-vs-pictify.json", "title": "Creatomate vs Pictify", "url": "https://www.anchorterminal.com/compare/creatomate-vs-pictify" }, { "json": "https://www.anchorterminal.com/compare/creatomate-vs-pixelixe.json", "title": "Creatomate vs Pixelixe", "url": "https://www.anchorterminal.com/compare/creatomate-vs-pixelixe" }, { "json": "https://www.anchorterminal.com/compare/dynapictures-vs-pictify.json", "title": "DynaPictures vs Pictify", "url": "https://www.anchorterminal.com/compare/dynapictures-vs-pictify" }, { "json": "https://www.anchorterminal.com/compare/dynapictures-vs-pixelixe.json", "title": "DynaPictures vs Pixelixe", "url": "https://www.anchorterminal.com/compare/dynapictures-vs-pixelixe" }, { "json": "https://www.anchorterminal.com/compare/layerre-vs-pictify.json", "title": "Layerre vs Pictify", "url": "https://www.anchorterminal.com/compare/layerre-vs-pictify" }, { "json": "https://www.anchorterminal.com/compare/layerre-vs-pixelixe.json", "title": "Layerre vs Pixelixe", "url": "https://www.anchorterminal.com/compare/layerre-vs-pixelixe" }, { "json": "https://www.anchorterminal.com/compare/photoroom-vs-pictify.json", "title": "Photoroom API vs Pictify", "url": "https://www.anchorterminal.com/compare/photoroom-vs-pictify" }, { "json": "https://www.anchorterminal.com/compare/pixelixe-vs-placid.json", "title": "Pixelixe vs Placid API + MCP", "url": "https://www.anchorterminal.com/compare/pixelixe-vs-placid" }, { "json": "https://www.anchorterminal.com/compare/pixelixe-vs-postnitro.json", "title": "Pixelixe vs PostNitro", "url": "https://www.anchorterminal.com/compare/pixelixe-vs-postnitro" }, { "json": "https://www.anchorterminal.com/compare/pixelixe-vs-robolly.json", "title": "Pixelixe vs Robolly", "url": "https://www.anchorterminal.com/compare/pixelixe-vs-robolly" }, { "json": "https://www.anchorterminal.com/compare/pixelixe-vs-shotstack.json", "title": "Pixelixe vs Shotstack", "url": "https://www.anchorterminal.com/compare/pixelixe-vs-shotstack" }, { "json": "https://www.anchorterminal.com/compare/pixelixe-vs-templated.json", "title": "Pixelixe vs Templated API + MCP", "url": "https://www.anchorterminal.com/compare/pixelixe-vs-templated" }, { "json": "https://www.anchorterminal.com/compare/abyssale-vs-pictify.json", "title": "Abyssale vs Pictify", "url": "https://www.anchorterminal.com/compare/abyssale-vs-pictify" }, { "json": "https://www.anchorterminal.com/compare/abyssale-vs-pixelixe.json", "title": "Abyssale vs Pixelixe", "url": "https://www.anchorterminal.com/compare/abyssale-vs-pixelixe" }, { "json": "https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-pictify.json", "title": "Adobe Photoshop API vs Pictify", "url": "https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-pictify" }, { "json": "https://www.anchorterminal.com/compare/osmo-cli-vs-pictify.json", "title": "Osmo CLI vs Pictify", "url": "https://www.anchorterminal.com/compare/osmo-cli-vs-pictify" }, { "json": "https://www.anchorterminal.com/compare/osmo-cli-vs-pixelixe.json", "title": "Osmo CLI vs Pixelixe", "url": "https://www.anchorterminal.com/compare/osmo-cli-vs-pixelixe" }, { "json": "https://www.anchorterminal.com/compare/pictify-vs-placid.json", "title": "Pictify vs Placid API + MCP", "url": "https://www.anchorterminal.com/compare/pictify-vs-placid" }, { "json": "https://www.anchorterminal.com/compare/pictify-vs-postnitro.json", "title": "Pictify vs PostNitro", "url": "https://www.anchorterminal.com/compare/pictify-vs-postnitro" }, { "json": "https://www.anchorterminal.com/compare/pictify-vs-robolly.json", "title": "Pictify vs Robolly", "url": "https://www.anchorterminal.com/compare/pictify-vs-robolly" }, { "json": "https://www.anchorterminal.com/compare/pictify-vs-shotstack.json", "title": "Pictify vs Shotstack", "url": "https://www.anchorterminal.com/compare/pictify-vs-shotstack" }, { "json": "https://www.anchorterminal.com/compare/pictify-vs-templated.json", "title": "Pictify vs Templated API + MCP", "url": "https://www.anchorterminal.com/compare/pictify-vs-templated" }, { "json": "https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-pixelixe.json", "title": "Adobe Photoshop API vs Pixelixe", "url": "https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-pixelixe" }, { "json": "https://www.anchorterminal.com/compare/photoroom-vs-pixelixe.json", "title": "Photoroom API vs Pixelixe", "url": "https://www.anchorterminal.com/compare/photoroom-vs-pixelixe" } ], "panel": null, "scores": [ { "by": 30, "edge": "pictify", "key": "reliability", "name": "Reliability", "pictify": 45, "pixelixe": 15, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 22, "edge": "pictify", "key": "schema", "name": "Schema \u0026 documentation", "pictify": 88, "pixelixe": 66, "weight": 13 }, { "by": 25, "edge": "pictify", "key": "ergonomics", "name": "Agent ergonomics", "pictify": 74, "pixelixe": 49, "weight": 13 }, { "by": 7, "edge": "pictify", "key": "security", "name": "Security \u0026 auth", "pictify": 45, "pixelixe": 38, "weight": 14 }, { "by": 10, "edge": "pictify", "key": "payments", "name": "Payments \u0026 pricing", "pictify": 40, "pixelixe": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 49, "edge": "pictify", "key": "maintenance", "name": "Maintenance \u0026 community", "pictify": 68, "pixelixe": 19, "weight": 7 }, { "by": 11, "edge": "pictify", "key": "transparency", "name": "Transparency \u0026 trust", "pictify": 52, "pixelixe": 41, "weight": 7 } ], "summary": "Pictify scores 55.7 (C) on agent readiness against Pixelixe's 37.3 (F), and leads in every scored category. Both do design rendering.", "tasks": null, "tutorials": [], "verdicts": { "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.", "pixelixe": "Pixelixe's seven MCP tools and their LLM-oriented reference make template fills and JSON-to-graphic creation simple to call, with an OpenAPI file for the core endpoints. Every error comes back as a 400 with a message, there are no published rate limits, status page or changelog, and API access starts at $59 a month." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/pictify-vs-pixelixe", "json": "https://www.anchorterminal.com/compare/pictify-vs-pixelixe.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/pictify-vs-pixelixe.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/pictify-vs-pixelixe.min.md" }, "markdown": "Pictify scores 55.7 (C) on agent readiness against Pixelixe's 37.3 (F), and leads in every scored category. Both do design rendering.\n\n- Pictify: grade C, 55.7/100, rank #861 of 1510. Markdown https://www.anchorterminal.com/tools/pictify.md · JSON https://www.anchorterminal.com/api/v1/tools/pictify.json\n- Pixelixe: grade F, 37.3/100, rank #1377 of 1510. Markdown https://www.anchorterminal.com/tools/pixelixe.md · JSON https://www.anchorterminal.com/api/v1/tools/pixelixe.json\n- Best programmatic image and design asset APIs for AI agents: https://www.anchorterminal.com/best/design-assets/index.md\n- All 153 assets comparisons: https://www.anchorterminal.com/compare/design-assets/index.md\n\n## Which one, for what\n\n### Pictify (C)\n\nGood for: HTML-to-image, template renders, PDFs and short video from one API, with per-render prices an agent can budget.\n\nAhead on:\n- Reliability, 45 against 15\n- Schema \u0026 documentation, 88 against 66\n- Agent ergonomics, 74 against 49\n- Security \u0026 auth, 45 against 38\n- Payments \u0026 pricing, 40 against 30\n- Maintenance \u0026 community, 68 against 19\n- Transparency \u0026 trust, 52 against 41\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: The MCP server sends tool arguments, results and the account email to PostHog unless turned off\n\n### Pixelixe (F)\n\nGood for: Template fills and white-label editing for marketing and SaaS teams, with a JSON-to-graphic route for agents.\n\nAlso in its favour:\n- No incidents deducted, where Pictify loses 3 points for them\n\nWatch for: Every error is HTTP 400 with a free-text message, including wrong keys and exhausted credits\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Pictify +49\n\n- 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.\n- 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.\n\n### Reliability: Pictify +30\n\n- 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.\n- 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.\n\n### Agent ergonomics: Pictify +25\n\n- 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.\n- 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.\n\n### Schema \u0026 documentation: Pictify +22\n\n- 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.\n- 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.\n\n### Transparency \u0026 trust: Pictify +11\n\n- 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.\n- 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.\n\n### Payments \u0026 pricing: Pictify +10\n\n- 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.\n- 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.\n\n## Score by category\n\n| Category | Weight | Pictify | Pixelixe | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 45 | 15 | Pictify +30 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 88 | 66 | Pictify +22 |\n| Agent ergonomics | 13% (16.2 this run) | 74 | 49 | Pictify +25 |\n| Security \u0026 auth | 14% (17.5 this run) | 45 | 38 | Pictify +7 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 30 | Pictify +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 68 | 19 | Pictify +49 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 52 | 41 | Pictify +11 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **55.7 · C** | **37.3 · F** | |\n\n## Facts side by side\n\n| Fact | Pictify | Pixelixe |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Pictify.io | Pixelixe |\n| Hosted endpoint | `https://api.pictify.io` | `https://studio.pixelixe.com/api` |\n| Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Paid |\n| Price for design rendering | $0.005 per image | not published |\n| x402 | no | no |\n| 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) |\n| Tools exposed | 25 | 7 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.github.pictify-io/mcp` | `com.pixelixe/pixelixe-mcp` |\n| Last release | 2026-09-20 | 2026-03-26 |\n| Terms last updated | 2024-07-18 | 2026-03-19 |\n| Privacy policy last updated | 2024-07-18 | 2026-04-07 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | yes |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 55 npm/wk | none |\n\n## Verdicts\n\n**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.\n\n**Pixelixe.** Pixelixe's seven MCP tools and their LLM-oriented reference make template fills and JSON-to-graphic creation simple to call, with an OpenAPI file for the core endpoints. Every error comes back as a 400 with a message, there are no published rate limits, status page or changelog, and API access starts at $59 a month.\n\n## Before you call either\n\n### Pictify\n\n1. Set `PICTIFY_ANALYTICS_DISABLED=1` in the MCP server's env when tool inputs are confidential\n2. On a 429, read `code` first; `quota_exceeded` means wait for the monthly reset, not retry\n3. Retry a 5xx once; a failed generation bills nothing\n4. Pass only one of `html`, `url` or `template` to `pictify_create_image`\n5. Use batch render for one image per row rather than many single calls\n\n### Pixelixe\n\n1. Call `pixelixe_search_documents` first to find the `document_uid` of the template to reuse\n2. Use `pixelixe_generate_graphic_variant` to fill an existing template; it can't change the layout\n3. Read the error `message` text, since every failure is a 400\n4. Stop and tell the user on 'Not enough Credits'; retrying won't help\n5. For a batch, use `pixelixe_create_multiple_images` and summarise counts rather than inlining every image\n\n## Questions\n\n### Which is better for AI agents, Pictify or Pixelixe?\n\nPictify scores 55.7 (C) on agent readiness against Pixelixe's 37.3 (F), and leads in every scored category.\n\n### Do Pictify and Pixelixe need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Pictify and Pixelixe without installing anything?\n\nYes. Pictify has a hosted endpoint at https://api.pictify.io and Pixelixe at https://studio.pixelixe.com/api.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/pictify-vs-pixelixe.json, and with the fewest tokens: https://www.anchorterminal.com/compare/pictify-vs-pixelixe.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"pictify\", \"b\": \"pixelixe\"}`. From a terminal: `anchor compare pictify pixelixe`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/pictify.json and https://www.anchorterminal.com/api/v1/tools/pixelixe.json\n\n## Other comparisons with Pictify or Pixelixe\n\n- [APITemplate.io vs Pictify](https://www.anchorterminal.com/compare/apitemplate-io-vs-pictify.md)\n- [APITemplate.io vs Pixelixe](https://www.anchorterminal.com/compare/apitemplate-io-vs-pixelixe.md)\n- [Bannerbear API + MCP vs Pictify](https://www.anchorterminal.com/compare/bannerbear-vs-pictify.md)\n- [Bannerbear API + MCP vs Pixelixe](https://www.anchorterminal.com/compare/bannerbear-vs-pixelixe.md)\n- [Canva REST APIs + MCP vs Pictify](https://www.anchorterminal.com/compare/canva-vs-pictify.md)\n- [Canva REST APIs + MCP vs Pixelixe](https://www.anchorterminal.com/compare/canva-vs-pixelixe.md)\n- [Contentdrips API and MCP vs Pictify](https://www.anchorterminal.com/compare/contentdrips-vs-pictify.md)\n- [Contentdrips API and MCP vs Pixelixe](https://www.anchorterminal.com/compare/contentdrips-vs-pixelixe.md)\n- [Creatomate vs Pictify](https://www.anchorterminal.com/compare/creatomate-vs-pictify.md)\n- [Creatomate vs Pixelixe](https://www.anchorterminal.com/compare/creatomate-vs-pixelixe.md)\n- [DynaPictures vs Pictify](https://www.anchorterminal.com/compare/dynapictures-vs-pictify.md)\n- [DynaPictures vs Pixelixe](https://www.anchorterminal.com/compare/dynapictures-vs-pixelixe.md)\n- [Layerre vs Pictify](https://www.anchorterminal.com/compare/layerre-vs-pictify.md)\n- [Layerre vs Pixelixe](https://www.anchorterminal.com/compare/layerre-vs-pixelixe.md)\n- [Photoroom API vs Pictify](https://www.anchorterminal.com/compare/photoroom-vs-pictify.md)\n- [Pixelixe vs Placid API + MCP](https://www.anchorterminal.com/compare/pixelixe-vs-placid.md)\n- [Pixelixe vs PostNitro](https://www.anchorterminal.com/compare/pixelixe-vs-postnitro.md)\n- [Pixelixe vs Robolly](https://www.anchorterminal.com/compare/pixelixe-vs-robolly.md)\n- [Pixelixe vs Shotstack](https://www.anchorterminal.com/compare/pixelixe-vs-shotstack.md)\n- [Pixelixe vs Templated API + MCP](https://www.anchorterminal.com/compare/pixelixe-vs-templated.md)\n- [Abyssale vs Pictify](https://www.anchorterminal.com/compare/abyssale-vs-pictify.md)\n- [Abyssale vs Pixelixe](https://www.anchorterminal.com/compare/abyssale-vs-pixelixe.md)\n- [Adobe Photoshop API vs Pictify](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-pictify.md)\n- [Osmo CLI vs Pictify](https://www.anchorterminal.com/compare/osmo-cli-vs-pictify.md)\n- [Osmo CLI vs Pixelixe](https://www.anchorterminal.com/compare/osmo-cli-vs-pixelixe.md)\n- [Pictify vs Placid API + MCP](https://www.anchorterminal.com/compare/pictify-vs-placid.md)\n- [Pictify vs PostNitro](https://www.anchorterminal.com/compare/pictify-vs-postnitro.md)\n- [Pictify vs Robolly](https://www.anchorterminal.com/compare/pictify-vs-robolly.md)\n- [Pictify vs Shotstack](https://www.anchorterminal.com/compare/pictify-vs-shotstack.md)\n- [Pictify vs Templated API + MCP](https://www.anchorterminal.com/compare/pictify-vs-templated.md)\n- [Adobe Photoshop API vs Pixelixe](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-pixelixe.md)\n- [Photoroom API vs Pixelixe](https://www.anchorterminal.com/compare/photoroom-vs-pixelixe.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Pictify vs Pixelixe", "url": "" } ], "description": "Pictify scores 55.7 (C) to Pixelixe's 37.3 (F) for design rendering. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Pictify C 55.7", "Pixelixe F 37.3", "scores" ], "h1": "Pictify vs Pixelixe", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/pictify-vs-pixelixe", "published": "2026-10-01", "section": "tools", "title": "Pictify vs Pixelixe for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/pictify-vs-pixelixe" }, "tokens": { "markdown": 4350, "slim": 2430 }, "version": 1 }