{ "data": { "a": { "slug": "abyssale", "name": "Abyssale", "vendor": "Abyssale SAS", "vendorUrl": "https://www.abyssale.com", "kind": "http-api", "category": "design-assets", "summary": "Abyssale is a creative automation platform from Paris that renders designs into images, MP4 video, GIFs, HTML5 banner ads and print PDFs, through a REST API, dynamic image URLs, webhooks, official SDKs and a remote MCP server.", "url": "https://www.anchorterminal.com/tools/abyssale", "markdownUrl": "https://www.anchorterminal.com/tools/abyssale.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/abyssale.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/abyssale.json", "dns": "abyssale.grade.anchorterminal.com", "license": "Closed service under the Abyssale terms of service (version 3, 21 July 2026)", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.abyssale.com", "packages": [ { "registry": "npm", "name": "@abyssale/sdk" }, { "registry": "pypi", "name": "abyssale" } ], "auth": "mixed", "authNotes": "REST uses a workspace API key in the `x-api-key` header, created in Workspace settings; test it with `POST /auth`. The MCP server at mcp.abyssale.com uses OAuth through Auth0 with per-tool scopes (`read:design`, `write:design`, `delete:design`, `import:design`, `generate:banner` and others), checked together with the user's workspace role. The two credentials are separate.", "pricing": "paid", "pricingNotes": "API and MCP come with Pro at $45 a seat a month ($36 yearly) and above; Start at $15 a seat has neither. Suite $75 a seat adds HTML5 and CMYK print PDF. 14-day free trial with no card. Generation credits are charged per format, 1 per image, 1 per second of video, GIF or HTML5, print PDFs by pixel area. Failed generations cost nothing.", "priceSummary": "$45 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "Seat subscriptions with credit balances. No x402, MPP or L402 in the OpenAPI, the developer docs or llms.txt (checked 2026-11-06). An empty balance returns 429 with an id, not a payment requirement.", "endpoints": [] }, "toolCount": 20, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://developers.abyssale.com/", "llmsTxt": "https://developers.abyssale.com/llms.txt", "openapi": "https://developers.abyssale.com/api.yaml", "registryName": "com.abyssale/mcp", "capabilities": [ "design.render", "design.templates", "design.brand", "image.edit", "pdf.generate", "video.generate" ], "tags": [ "hosted", "openapi", "llms-txt", "mcp", "remote-mcp", "mcp-registry", "oauth", "api-key", "webhooks", "sdk", "trial", "no-card", "eu" ], "lastRelease": "2026-10-29", "graded": true, "anchor": { "graded": true, "score": 65.6, "grade": "B", "agentReady": false, "rank": 413, "ranked": true, "rankOf": 1510, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 85, "maintenance": 85, "payments": 35, "reliability": 41, "schema": 98, "security": 55, "transparency": 71 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Abyssale publishes a full OpenAPI file, dated versions, tiered rate limits with Retry-After, one error envelope and per-tool OAuth scopes on its MCP server. API access starts at $45 a seat a month after a 14-day trial, and no status page or published SLA was found.", "bestFor": "Multi-format ad creative, video, HTML5 banners and print PDFs from one design, for marketing teams and agencies with an agent in the loop.", "strengths": [ "OpenAPI file, a detailed llms.txt and a dated changelog that lists breaking changes first", "Published rate-limit tiers with X-RateLimit headers, Retry-After and distinct 429 ids", "MCP scopes per tool group, so a client can read designs without spending credits or deleting", "Credit cost per output published to the format, and failed generations aren't charged", "Official Node.js and Python SDKs with retry and polling helpers, released October 2026" ], "weaknesses": [ "API and MCP need the Pro plan at $45 a seat a month", "No status page found, and the SLA is negotiated for Enterprise only", "AI training on anonymised customer content is on by default", "Design import, the JSON authoring route, is alpha and outside the deprecation policy", "No security.txt, disclosure policy or certification found" ], "agentNotes": [ "Branch on the error `id`, never the message; `request_rate_limited` means wait Retry-After seconds", "Multiply credits by formats before a batch, since 200 products in 6 formats cost 1,200 credits", "Ask the MCP user to approve only `read:design` unless the task must generate or change designs", "Use asynchronous generation for several formats and deduplicate webhooks on `X-Abyssale-Delivery-Id`", "Check `GET /credits` first; it costs nothing and shows both balances" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 65.6 } ], "editorialScores": { "ergonomics": 85, "maintenance": 85, "payments": 35, "reliability": 41, "schema": 98, "security": 55, "transparency": 69 }, "provenanceScore": 72, "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": "npm install @abyssale/sdk", "http": "curl -X POST https://api.abyssale.com/auth -H \"x-api-key: $ABYSSALE_API_KEY\"", "claudeCode": "claude mcp add --transport http --client-id tpc_iJ7LWqVdzR7c7jf21gMqDQ --callback-port 3418 -s user abyssale_prod https://mcp.abyssale.com/mcp" }, "letme": { "capability": "https://letme.dev/design.render", "tool": "https://letme.dev/abyssale" }, "area": "design-diagrams", "unitPrices": [ { "item": "Pro seat (API and MCP)", "unit": "seat-month", "usd": 45, "note": "$36 billed yearly; the Start plan at $15 has no API" }, { "item": "Suite seat", "unit": "seat-month", "usd": 75, "note": "$60 billed yearly; adds HTML5 ads and CMYK print PDF" } ], "provenance": { "legalEntity": "Abyssale SAS", "domain": "abyssale.com", "domainRegistered": "2018-07-10", "endpointOnVendorDomain": true, "terms": "https://www.abyssale.com/terms-of-service", "privacy": "https://www.abyssale.com/privacy-policy", "statusPage": "", "changelog": "https://developers.abyssale.com/rest-api/changelog", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The terms (version 3, 21 July 2026) and the legal notice name ABYSSALE, an SAS at 49 rue de Ponthieu, 75008 Paris, Paris RCS 878 526 573. The terms give share capital as €1,980.00 and the legal notice as €1,902.80.", "The terms forbid extracting, scraping or reusing the platform's databases, including the public template database. Public docs and policy pages were read as data.", "www.abyssale.com/robots.txt and developers.abyssale.com/robots.txt allow all paths.", "/.well-known/security.txt returns 404. No status page was linked from the site or the docs, and status.abyssale.com did not answer.", "RDAP gives abyssale.com a registration date of 10 July 2018." ], "score": 72 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/abyssale.json", "live": { "slug": "abyssale", "probe": { "target": "https://api.abyssale.com", "method": "get", "lastAt": "2026-11-07T19:21:50.015154604Z", "lastOk": true, "lastStatus": 404, "lastMs": 99, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 68, "p95ms24h": 171, "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.abyssale/mcp", "version": "1.0.1", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "npm", "name": "@abyssale/sdk", "version": "1.9.0", "seenAt": "2026-11-06T23:02:19.286863658Z" }, { "registry": "pypi", "name": "abyssale", "version": "1.7.0", "released": "2026-10-21", "seenAt": "2026-11-06T23:02:19.747808303Z" } ], "npmWeekly": 29, "pypiWeekly": 49, "securityTxt": { "url": "https://abyssale.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:33.168565397Z" }, "llmsTxt": { "url": "https://developers.abyssale.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:04.477678741Z" }, "pages": [ { "url": "https://developers.abyssale.com/rest-api/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:03:36.173334461Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1c916e422299" }, { "url": "https://www.abyssale.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:24:07.939253804Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1756c40b8e19" }, { "url": "https://www.abyssale.com/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:24:10.078462035Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "982f9b4f8587" } ], "updatedAt": "2026-11-07T19:21:50.015154604Z" } }, "answer": "Abyssale scores 65.6 (B) 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": 66, "category": "maintenance", "leads": "abyssale", "name": "Maintenance \u0026 community", "reasons": { "a": "API version v2026-10-29, eight days before this check (30). Fifteen dated API versions between 21 August and 29 October, MCP server releases 1.0.0 (1 September) to 1.2.0 (7 October), and SDK releases in October (20). Closed service with a changelog and RSS feed, help@abyssale.com and in-app chat, which we didn't test (12 of 15). com.abyssale/mcp is in the official MCP registry under a domain-verified namespace, and the Node.js (1.9.0) and Python (1.7.0) SDKs were both released on 21 October 2026 (15). Both SDKs are current; their repositories weren't read (8 of 10). 30 + 20 + 12 + 15 + 8 = 85.", "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": 85, "b": 19 } }, { "by": 36, "category": "ergonomics", "leads": "abyssale", "name": "Agent ergonomics", "reasons": { "a": "20 MCP tools (15 for 11 to 30), plus 5 because OAuth scopes per tool group let a client be approved for reads only (20 of 25). Design listings search by words in any order, filter by project, orientation, size, format and dates, sort and order, and say honestly when a page is past the end; listing tools refuse unsupported options rather than ignore them, per MCP 1.2.0 (19 of 20). One envelope with an `id` to branch on, and error docs that say which errors a retry never fixes (19 of 20). The permissions page marks each tool read-only, mutating or destructive, but MCP annotations couldn't be confirmed on the closed server, and generation has no idempotency key (12 of 20). Official Node.js and Python SDKs with retry behaviour and polling helpers (15). 20 + 19 + 19 + 12 + 15 = 85.", "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": 85, "b": 49 } }, { "by": 32, "category": "schema", "leads": "abyssale", "name": "Schema \u0026 documentation", "reasons": { "a": "A 424 KB OpenAPI file at developers.abyssale.com/api.yaml with 34 operations, from which the reference pages are generated (25). A detailed llms.txt that states the base URL, auth, rate limits, error envelope and webhook signing up front (10). Pages say what each endpoint is for and when to use another, such as synchronous versus asynchronous generation and designs versus workspace templates, and the MCP permissions page says what each tool can break (19 of 20). Typed parameters with enums, ranges and required fields across layers and formats (14 of 15). One error envelope everywhere, an error catalogue with machine-readable ids and what to do for each, and worked examples (15). Date-based versions named in every response and a dated changelog in Keep a Changelog form with a Breaking section first; the MCP server has its own semver changelog (15). 25 + 10 + 19 + 14 + 15 + 15 = 98.", "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": 98, "b": 66 } }, { "by": 30, "category": "transparency", "leads": "abyssale", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under terms of service version 3 of 21 July 2026, from a Paris SAS with its register number (15). The privacy policy and terms agree on EU hosting on AWS Ireland, deletion timelines and breach notice within 72 hours, but AI model training on anonymised customer content is on by default with a workspace opt-out, and anonymised data may be kept indefinitely (20 of 30). The changelog has Deprecated and Removed sections and refers to a deprecation policy that covers stable endpoints but not alpha ones; the policy's notice period wasn't found (14 of 20). Subprocessors named with locations, among them AWS Ireland, Auth0, Brevo, Intercom and AI providers including OpenAI, Anthropic, Black Forest Labs and Google, some outside the EEA (20). 15 + 20 + 14 + 20 = 69.", "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": 71, "b": 41 } }, { "by": 26, "category": "reliability", "leads": "abyssale", "name": "Reliability", "reasons": { "a": "Hosted lines, for the REST API and the remote MCP server. No status page was linked from the site or the docs, and status.abyssale.com did not answer (0). No readable incident history (5). Rate limits published in full, 10 requests a second globally and per-workspace tiers with per-minute and per-hour budgets (15). 429s carry Retry-After and X-RateLimit headers, three 429 ids say which limit was hit, failed generations cost nothing, and webhooks carry a delivery id to deduplicate on. No idempotency key on generation requests (13 of 15). The terms promise best-effort availability and leave SLAs to Enterprise contracts, so none is published (0). Generation and the MCP server are generally available, while Design Import, the JSON authoring route, is labelled alpha (8 of 10). 0 + 5 + 15 + 13 + 0 + 8 = 41.", "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": 41, "b": 15 } }, { "by": 17, "category": "security", "leads": "abyssale", "name": "Security \u0026 auth", "reasons": { "a": "The MCP server uses OAuth through Auth0 with scopes per tool group (`read:design`, `write:design`, `delete:design`, `import:design`, `generate:banner`, `read:credits` and others), enforced alongside the user's workspace role, and approval is per client connection. The REST API uses a workspace `x-api-key` with no scopes documented (28 of 30). A client can be approved for reads only, and deleting needs its own scope, but nothing on the server asks for confirmation; the docs leave that to the client per the MCP spec (17 of 20). Tools return the workspace's own designs and fonts; image layers can point at outside URLs (10 of 15). No audit log or per-call record was found (0). No security.txt, disclosure policy, bug bounty or certification found (0). 28 + 17 + 10 + 0 + 0 = 55.", "b": "A bearer API key per account, plus a public key for the embedded editor. The MCP server accepts the key or an OAuth token from studio.pixelixe.com/oauth/mcp with one `pixelixe.mcp` scope. No key scopes, rotation or revocation documented (18 of 30). No read-only mode, though the MCP tools can't delete or change account settings (10 of 20). Tools return the account's own templates and renders (10 of 15). No audit log or per-call record documented (0). No security.txt, disclosure policy, bug bounty or certification found (0). 18 + 10 + 10 + 0 + 0 = 38." }, "scores": { "a": 55, "b": 38 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Abyssale SAS", "b": "Pixelixe", "name": "Vendor" }, { "a": "https://api.abyssale.com", "b": "https://studio.pixelixe.com/api", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Closed service under the Abyssale terms of service (version 3, 21 July 2026)", "b": "Closed service under the Pixelixe terms of service (last modified 19 March 2026)", "name": "Licence" }, { "a": "20", "b": "7", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "com.abyssale/mcp", "b": "com.pixelixe/pixelixe-mcp", "name": "MCP registry" }, { "a": "2026-10-29", "b": "2026-03-26", "name": "Last release" }, { "a": "no date given", "b": "2026-03-19", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-04-07", "name": "Privacy policy last updated" }, { "a": "yes", "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" } ], "faq": [ { "answer": "Abyssale scores 65.6 (B) on agent readiness against Pixelixe's 37.3 (F), and leads in every scored category.", "question": "Which is better for AI agents, Abyssale or Pixelixe?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Abyssale and Pixelixe need an API key?" }, { "answer": "Yes. Abyssale has a hosted endpoint at https://api.abyssale.com and Pixelixe at https://studio.pixelixe.com/api.", "question": "Can an agent call Abyssale and Pixelixe without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 41 against 15", "Schema \u0026 documentation, 98 against 66", "Agent ergonomics, 85 against 49", "Security \u0026 auth, 55 against 38", "Payments \u0026 pricing, 35 against 30", "Maintenance \u0026 community, 85 against 19", "Transparency \u0026 trust, 71 against 41" ], "also": null, "goodFor": "Multi-format ad creative, video, HTML5 banners and print PDFs from one design, for marketing teams and agencies with an agent in the loop.", "slug": "abyssale", "watchFor": "API and MCP need the Pro plan at $45 a seat a month" }, { "aheadOn": null, "also": null, "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-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-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-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-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-pixelixe.json", "title": "Creatomate vs Pixelixe", "url": "https://www.anchorterminal.com/compare/creatomate-vs-pixelixe" }, { "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-pixelixe.json", "title": "Layerre vs Pixelixe", "url": "https://www.anchorterminal.com/compare/layerre-vs-pixelixe" }, { "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-adobe-photoshop-api.json", "title": "Abyssale vs Adobe Photoshop API", "url": "https://www.anchorterminal.com/compare/abyssale-vs-adobe-photoshop-api" }, { "json": "https://www.anchorterminal.com/compare/abyssale-vs-apitemplate-io.json", "title": "Abyssale vs APITemplate.io", "url": "https://www.anchorterminal.com/compare/abyssale-vs-apitemplate-io" }, { "json": "https://www.anchorterminal.com/compare/abyssale-vs-bannerbear.json", "title": "Abyssale vs Bannerbear API + MCP", "url": "https://www.anchorterminal.com/compare/abyssale-vs-bannerbear" }, { "json": "https://www.anchorterminal.com/compare/abyssale-vs-canva.json", "title": "Abyssale vs Canva REST APIs + MCP", "url": "https://www.anchorterminal.com/compare/abyssale-vs-canva" }, { "json": "https://www.anchorterminal.com/compare/abyssale-vs-contentdrips.json", "title": "Abyssale vs Contentdrips API and MCP", "url": "https://www.anchorterminal.com/compare/abyssale-vs-contentdrips" }, { "json": "https://www.anchorterminal.com/compare/abyssale-vs-creatomate.json", "title": "Abyssale vs Creatomate", "url": "https://www.anchorterminal.com/compare/abyssale-vs-creatomate" }, { "json": "https://www.anchorterminal.com/compare/abyssale-vs-dynapictures.json", "title": "Abyssale vs DynaPictures", "url": "https://www.anchorterminal.com/compare/abyssale-vs-dynapictures" }, { "json": "https://www.anchorterminal.com/compare/abyssale-vs-layerre.json", "title": "Abyssale vs Layerre", "url": "https://www.anchorterminal.com/compare/abyssale-vs-layerre" }, { "json": "https://www.anchorterminal.com/compare/abyssale-vs-osmo-cli.json", "title": "Abyssale vs Osmo CLI", "url": "https://www.anchorterminal.com/compare/abyssale-vs-osmo-cli" }, { "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-placid.json", "title": "Abyssale vs Placid API + MCP", "url": "https://www.anchorterminal.com/compare/abyssale-vs-placid" }, { "json": "https://www.anchorterminal.com/compare/abyssale-vs-postnitro.json", "title": "Abyssale vs PostNitro", "url": "https://www.anchorterminal.com/compare/abyssale-vs-postnitro" }, { "json": "https://www.anchorterminal.com/compare/abyssale-vs-robolly.json", "title": "Abyssale vs Robolly", "url": "https://www.anchorterminal.com/compare/abyssale-vs-robolly" }, { "json": "https://www.anchorterminal.com/compare/abyssale-vs-shotstack.json", "title": "Abyssale vs Shotstack", "url": "https://www.anchorterminal.com/compare/abyssale-vs-shotstack" }, { "json": "https://www.anchorterminal.com/compare/abyssale-vs-templated.json", "title": "Abyssale vs Templated API + MCP", "url": "https://www.anchorterminal.com/compare/abyssale-vs-templated" }, { "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-pixelixe.json", "title": "Pictify vs Pixelixe", "url": "https://www.anchorterminal.com/compare/pictify-vs-pixelixe" }, { "json": "https://www.anchorterminal.com/compare/abyssale-vs-photoroom.json", "title": "Abyssale vs Photoroom API", "url": "https://www.anchorterminal.com/compare/abyssale-vs-photoroom" }, { "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": [ { "abyssale": 41, "by": 26, "edge": "abyssale", "key": "reliability", "name": "Reliability", "pixelixe": 15, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "abyssale": 98, "by": 32, "edge": "abyssale", "key": "schema", "name": "Schema \u0026 documentation", "pixelixe": 66, "weight": 13 }, { "abyssale": 85, "by": 36, "edge": "abyssale", "key": "ergonomics", "name": "Agent ergonomics", "pixelixe": 49, "weight": 13 }, { "abyssale": 55, "by": 17, "edge": "abyssale", "key": "security", "name": "Security \u0026 auth", "pixelixe": 38, "weight": 14 }, { "abyssale": 35, "by": 5, "edge": "abyssale", "key": "payments", "name": "Payments \u0026 pricing", "pixelixe": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "abyssale": 85, "by": 66, "edge": "abyssale", "key": "maintenance", "name": "Maintenance \u0026 community", "pixelixe": 19, "weight": 7 }, { "abyssale": 71, "by": 30, "edge": "abyssale", "key": "transparency", "name": "Transparency \u0026 trust", "pixelixe": 41, "weight": 7 } ], "summary": "Abyssale scores 65.6 (B) on agent readiness against Pixelixe's 37.3 (F), and leads in every scored category. Both do design rendering.", "tasks": null, "tutorials": [], "verdicts": { "abyssale": "Abyssale publishes a full OpenAPI file, dated versions, tiered rate limits with Retry-After, one error envelope and per-tool OAuth scopes on its MCP server. API access starts at $45 a seat a month after a 14-day trial, and no status page or published SLA was found.", "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/abyssale-vs-pixelixe", "json": "https://www.anchorterminal.com/compare/abyssale-vs-pixelixe.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/abyssale-vs-pixelixe.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/abyssale-vs-pixelixe.min.md" }, "markdown": "Abyssale scores 65.6 (B) on agent readiness against Pixelixe's 37.3 (F), and leads in every scored category. Both do design rendering.\n\n- Abyssale: grade B, 65.6/100, rank #413 of 1510. Markdown https://www.anchorterminal.com/tools/abyssale.md · JSON https://www.anchorterminal.com/api/v1/tools/abyssale.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### Abyssale (B)\n\nGood for: Multi-format ad creative, video, HTML5 banners and print PDFs from one design, for marketing teams and agencies with an agent in the loop.\n\nAhead on:\n- Reliability, 41 against 15\n- Schema \u0026 documentation, 98 against 66\n- Agent ergonomics, 85 against 49\n- Security \u0026 auth, 55 against 38\n- Payments \u0026 pricing, 35 against 30\n- Maintenance \u0026 community, 85 against 19\n- Transparency \u0026 trust, 71 against 41\n\nWatch for: API and MCP need the Pro plan at $45 a seat a month\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\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: Abyssale +66\n\n- Abyssale (85): API version v2026-10-29, eight days before this check (30). Fifteen dated API versions between 21 August and 29 October, MCP server releases 1.0.0 (1 September) to 1.2.0 (7 October), and SDK releases in October (20). Closed service with a changelog and RSS feed, help@abyssale.com and in-app chat, which we didn't test (12 of 15). com.abyssale/mcp is in the official MCP registry under a domain-verified namespace, and the Node.js (1.9.0) and Python (1.7.0) SDKs were both released on 21 October 2026 (15). Both SDKs are current; their repositories weren't read (8 of 10). 30 + 20 + 12 + 15 + 8 = 85.\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### Agent ergonomics: Abyssale +36\n\n- Abyssale (85): 20 MCP tools (15 for 11 to 30), plus 5 because OAuth scopes per tool group let a client be approved for reads only (20 of 25). Design listings search by words in any order, filter by project, orientation, size, format and dates, sort and order, and say honestly when a page is past the end; listing tools refuse unsupported options rather than ignore them, per MCP 1.2.0 (19 of 20). One envelope with an `id` to branch on, and error docs that say which errors a retry never fixes (19 of 20). The permissions page marks each tool read-only, mutating or destructive, but MCP annotations couldn't be confirmed on the closed server, and generation has no idempotency key (12 of 20). Official Node.js and Python SDKs with retry behaviour and polling helpers (15). 20 + 19 + 19 + 12 + 15 = 85.\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: Abyssale +32\n\n- Abyssale (98): A 424 KB OpenAPI file at developers.abyssale.com/api.yaml with 34 operations, from which the reference pages are generated (25). A detailed llms.txt that states the base URL, auth, rate limits, error envelope and webhook signing up front (10). Pages say what each endpoint is for and when to use another, such as synchronous versus asynchronous generation and designs versus workspace templates, and the MCP permissions page says what each tool can break (19 of 20). Typed parameters with enums, ranges and required fields across layers and formats (14 of 15). One error envelope everywhere, an error catalogue with machine-readable ids and what to do for each, and worked examples (15). Date-based versions named in every response and a dated changelog in Keep a Changelog form with a Breaking section first; the MCP server has its own semver changelog (15). 25 + 10 + 19 + 14 + 15 + 15 = 98.\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: Abyssale +30\n\n- Abyssale (71): Closed service under terms of service version 3 of 21 July 2026, from a Paris SAS with its register number (15). The privacy policy and terms agree on EU hosting on AWS Ireland, deletion timelines and breach notice within 72 hours, but AI model training on anonymised customer content is on by default with a workspace opt-out, and anonymised data may be kept indefinitely (20 of 30). The changelog has Deprecated and Removed sections and refers to a deprecation policy that covers stable endpoints but not alpha ones; the policy's notice period wasn't found (14 of 20). Subprocessors named with locations, among them AWS Ireland, Auth0, Brevo, Intercom and AI providers including OpenAI, Anthropic, Black Forest Labs and Google, some outside the EEA (20). 15 + 20 + 14 + 20 = 69.\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### Reliability: Abyssale +26\n\n- Abyssale (41): Hosted lines, for the REST API and the remote MCP server. No status page was linked from the site or the docs, and status.abyssale.com did not answer (0). No readable incident history (5). Rate limits published in full, 10 requests a second globally and per-workspace tiers with per-minute and per-hour budgets (15). 429s carry Retry-After and X-RateLimit headers, three 429 ids say which limit was hit, failed generations cost nothing, and webhooks carry a delivery id to deduplicate on. No idempotency key on generation requests (13 of 15). The terms promise best-effort availability and leave SLAs to Enterprise contracts, so none is published (0). Generation and the MCP server are generally available, while Design Import, the JSON authoring route, is labelled alpha (8 of 10). 0 + 5 + 15 + 13 + 0 + 8 = 41.\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### Security \u0026 auth: Abyssale +17\n\n- Abyssale (55): The MCP server uses OAuth through Auth0 with scopes per tool group (`read:design`, `write:design`, `delete:design`, `import:design`, `generate:banner`, `read:credits` and others), enforced alongside the user's workspace role, and approval is per client connection. The REST API uses a workspace `x-api-key` with no scopes documented (28 of 30). A client can be approved for reads only, and deleting needs its own scope, but nothing on the server asks for confirmation; the docs leave that to the client per the MCP spec (17 of 20). Tools return the workspace's own designs and fonts; image layers can point at outside URLs (10 of 15). No audit log or per-call record was found (0). No security.txt, disclosure policy, bug bounty or certification found (0). 28 + 17 + 10 + 0 + 0 = 55.\n- Pixelixe (38): A bearer API key per account, plus a public key for the embedded editor. The MCP server accepts the key or an OAuth token from studio.pixelixe.com/oauth/mcp with one `pixelixe.mcp` scope. No key scopes, rotation or revocation documented (18 of 30). No read-only mode, though the MCP tools can't delete or change account settings (10 of 20). Tools return the account's own templates and renders (10 of 15). No audit log or per-call record documented (0). No security.txt, disclosure policy, bug bounty or certification found (0). 18 + 10 + 10 + 0 + 0 = 38.\n\n## Score by category\n\n| Category | Weight | Abyssale | Pixelixe | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 41 | 15 | Abyssale +26 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 98 | 66 | Abyssale +32 |\n| Agent ergonomics | 13% (16.2 this run) | 85 | 49 | Abyssale +36 |\n| Security \u0026 auth | 14% (17.5 this run) | 55 | 38 | Abyssale +17 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 30 | Abyssale +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 85 | 19 | Abyssale +66 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 71 | 41 | Abyssale +30 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **65.6 · B** | **37.3 · F** | |\n\n## Facts side by side\n\n| Fact | Abyssale | Pixelixe |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Abyssale SAS | Pixelixe |\n| Hosted endpoint | `https://api.abyssale.com` | `https://studio.pixelixe.com/api` |\n| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| Licence | Closed service under the Abyssale terms of service (version 3, 21 July 2026) | Closed service under the Pixelixe terms of service (last modified 19 March 2026) |\n| Tools exposed | 20 | 7 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `com.abyssale/mcp` | `com.pixelixe/pixelixe-mcp` |\n| Last release | 2026-10-29 | 2026-03-26 |\n| Terms last updated | no date given | 2026-03-19 |\n| Privacy policy last updated | no date given | 2026-04-07 |\n| Customer content may train models | yes | 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\n## Verdicts\n\n**Abyssale.** Abyssale publishes a full OpenAPI file, dated versions, tiered rate limits with Retry-After, one error envelope and per-tool OAuth scopes on its MCP server. API access starts at $45 a seat a month after a 14-day trial, and no status page or published SLA was found.\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### Abyssale\n\n1. Branch on the error `id`, never the message; `request_rate_limited` means wait Retry-After seconds\n2. Multiply credits by formats before a batch, since 200 products in 6 formats cost 1,200 credits\n3. Ask the MCP user to approve only `read:design` unless the task must generate or change designs\n4. Use asynchronous generation for several formats and deduplicate webhooks on `X-Abyssale-Delivery-Id`\n5. Check `GET /credits` first; it costs nothing and shows both balances\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, Abyssale or Pixelixe?\n\nAbyssale scores 65.6 (B) on agent readiness against Pixelixe's 37.3 (F), and leads in every scored category.\n\n### Do Abyssale and Pixelixe need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Abyssale and Pixelixe without installing anything?\n\nYes. Abyssale has a hosted endpoint at https://api.abyssale.com and Pixelixe at https://studio.pixelixe.com/api.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/abyssale-vs-pixelixe.json, and with the fewest tokens: https://www.anchorterminal.com/compare/abyssale-vs-pixelixe.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"abyssale\", \"b\": \"pixelixe\"}`. From a terminal: `anchor compare abyssale pixelixe`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/abyssale.json and https://www.anchorterminal.com/api/v1/tools/pixelixe.json\n\n## Other comparisons with Abyssale or Pixelixe\n\n- [APITemplate.io vs Pixelixe](https://www.anchorterminal.com/compare/apitemplate-io-vs-pixelixe.md)\n- [Bannerbear API + MCP vs Pixelixe](https://www.anchorterminal.com/compare/bannerbear-vs-pixelixe.md)\n- [Canva REST APIs + MCP vs Pixelixe](https://www.anchorterminal.com/compare/canva-vs-pixelixe.md)\n- [Contentdrips API and MCP vs Pixelixe](https://www.anchorterminal.com/compare/contentdrips-vs-pixelixe.md)\n- [Creatomate vs Pixelixe](https://www.anchorterminal.com/compare/creatomate-vs-pixelixe.md)\n- [DynaPictures vs Pixelixe](https://www.anchorterminal.com/compare/dynapictures-vs-pixelixe.md)\n- [Layerre vs Pixelixe](https://www.anchorterminal.com/compare/layerre-vs-pixelixe.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 Adobe Photoshop API](https://www.anchorterminal.com/compare/abyssale-vs-adobe-photoshop-api.md)\n- [Abyssale vs APITemplate.io](https://www.anchorterminal.com/compare/abyssale-vs-apitemplate-io.md)\n- [Abyssale vs Bannerbear API + MCP](https://www.anchorterminal.com/compare/abyssale-vs-bannerbear.md)\n- [Abyssale vs Canva REST APIs + MCP](https://www.anchorterminal.com/compare/abyssale-vs-canva.md)\n- [Abyssale vs Contentdrips API and MCP](https://www.anchorterminal.com/compare/abyssale-vs-contentdrips.md)\n- [Abyssale vs Creatomate](https://www.anchorterminal.com/compare/abyssale-vs-creatomate.md)\n- [Abyssale vs DynaPictures](https://www.anchorterminal.com/compare/abyssale-vs-dynapictures.md)\n- [Abyssale vs Layerre](https://www.anchorterminal.com/compare/abyssale-vs-layerre.md)\n- [Abyssale vs Osmo CLI](https://www.anchorterminal.com/compare/abyssale-vs-osmo-cli.md)\n- [Abyssale vs Pictify](https://www.anchorterminal.com/compare/abyssale-vs-pictify.md)\n- [Abyssale vs Placid API + MCP](https://www.anchorterminal.com/compare/abyssale-vs-placid.md)\n- [Abyssale vs PostNitro](https://www.anchorterminal.com/compare/abyssale-vs-postnitro.md)\n- [Abyssale vs Robolly](https://www.anchorterminal.com/compare/abyssale-vs-robolly.md)\n- [Abyssale vs Shotstack](https://www.anchorterminal.com/compare/abyssale-vs-shotstack.md)\n- [Abyssale vs Templated API + MCP](https://www.anchorterminal.com/compare/abyssale-vs-templated.md)\n- [Osmo CLI vs Pixelixe](https://www.anchorterminal.com/compare/osmo-cli-vs-pixelixe.md)\n- [Pictify vs Pixelixe](https://www.anchorterminal.com/compare/pictify-vs-pixelixe.md)\n- [Abyssale vs Photoroom API](https://www.anchorterminal.com/compare/abyssale-vs-photoroom.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": "Abyssale vs Pixelixe", "url": "" } ], "description": "Abyssale scores 65.6 (B) to Pixelixe's 37.3 (F) for design rendering. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Abyssale B 65.6", "Pixelixe F 37.3", "scores" ], "h1": "Abyssale vs Pixelixe", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/abyssale-vs-pixelixe", "published": "2026-10-01", "section": "tools", "title": "Abyssale vs Pixelixe for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/abyssale-vs-pixelixe" }, "tokens": { "markdown": 4600, "slim": 2730 }, "version": 1 }