{ "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 Robolly's 48.4 (D), and leads in 5 of 7 scored categories. Robolly leads on reliability.", "b": { "slug": "robolly", "name": "Robolly", "vendor": "Avantis Innovations LLC (Robolly)", "vendorUrl": "https://robolly.com", "kind": "http-api", "category": "design-assets", "summary": "Robolly renders templates designed in its visual editor into JPG, PNG, WebP, single and multi-page PDF, MP4 and WebM files, through an on-demand REST API, signed render links, no-code integrations and a remote MCP server.", "url": "https://www.anchorterminal.com/tools/robolly", "markdownUrl": "https://www.anchorterminal.com/tools/robolly.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/robolly.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/robolly.json", "dns": "robolly.grade.anchorterminal.com", "license": "Closed service under the Robolly terms of use (effective 8 April 2026)", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.robolly.com/v1", "packages": [], "auth": "mixed", "authNotes": "API key from Account settings, sent as `Authorization: Bearer`; render links can instead carry a signature. The remote MCP server at api.robolly.com/mcp uses OAuth with one `robolly:mcp` scope, where the user picks the organisation it may reach, and connections are listed and revoked under Account settings \u003e Connected AI Tools. The API key works as a fallback bearer token. No key scopes documented.", "pricing": "paid", "pricingNotes": "Individual $39 a month (250 or 1,000 render credits), Business $129 a month (10,000 to 500,000 credits by tier), Enterprise custom above 1,000,000. 7-day trial with no card. 1 credit for a JPG or WebP under 2,000 px, 3 for PNG, more for larger sizes, PDFs and video. Identical re-renders within 45 days are free.", "priceSummary": "$39 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "Monthly plans with render credits. No x402, MPP or L402 in the API reference, the MCP page, llms.txt or pricing (checked 2026-11-06). Exhausted credits return the error code `render-limit-exhausted`.", "endpoints": [] }, "toolCount": 9, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://robolly.com/docs/api-reference/", "llmsTxt": "https://robolly.com/llms.txt", "capabilities": [ "design.templates", "design.render", "pdf.generate", "video.generate" ], "tags": [ "hosted", "mcp", "remote-mcp", "oauth", "api-key", "llms-txt", "trial", "no-card", "status-page" ], "graded": true, "anchor": { "graded": true, "score": 48.4, "grade": "D", "agentReady": false, "rank": 1127, "ranked": true, "rankOf": 1510, "categoryRank": 11, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 5, "payments": 35, "reliability": 48, "schema": 57, "security": 47, "transparency": 49 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "Robolly's nine MCP tools, synchronous renders, typed error codes and free cached re-renders keep template rendering cheap and predictable for an agent, and OAuth connections can be revoked per client. There is no OpenAPI file, changelog or dated release, and API access starts at $39 a month after a 7-day trial.", "bestFor": "Template-driven images, PDFs and short videos for marketers and developers who want a hosted editor and simple synchronous calls.", "strengths": [ "Nine compact MCP tools, including one that lists each template's accepted keys and constraints", "Error responses carry `errorCode` slugs, among them `rate-limit` and `render-limit-exhausted`", "Identical re-renders within 45 days are served free from cache", "MCP OAuth limited to one organisation, with connections revoked in Account settings", "Published rate limit of 3 renders a second and a credit table by format and size" ], "weaknesses": [ "No OpenAPI or other machine-readable contract found", "No changelog or dated release found, and the MCP server isn't in the official registry", "API access needs a paid plan from $39 a month after a 7-day trial", "The UptimeRobot status page draws its data from a path its robots.txt closes to us", "The privacy policy names no hosting or other processors" ], "agentNotes": [ "Call `get_template_modifications` before `render` to learn the keys a template accepts", "Send renders one at a time; the API refuses more than 3 a second with `rate-limit`", "Repeat an identical render freely; it is cached for 45 days and costs nothing", "Poll `get_render` after `render_video`, since video renders are queued", "Stop on `render-limit-exhausted` and tell the user the monthly credits are spent" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 48.4 } ], "editorialScores": { "ergonomics": 75, "maintenance": 5, "payments": 35, "reliability": 48, "schema": 57, "security": 47, "transparency": 27 }, "provenanceScore": 71, "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": { "claudeCode": "claude mcp add --transport http robolly --scope user https://api.robolly.com/mcp", "config": { "mcpServers": { "robolly": { "type": "http", "url": "https://api.robolly.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/design.templates", "tool": "https://letme.dev/robolly" }, "area": "design-diagrams", "unitPrices": [ { "item": "Individual plan", "unit": "month", "usd": 39, "note": "From 250 render credits a month; more credits cost more" }, { "item": "Business plan", "unit": "month", "usd": 129, "note": "From 10,000 render credits a month" } ], "provenance": { "legalEntity": "Avantis Innovations LLC", "domain": "robolly.com", "domainRegistered": "2021-01-30", "endpointOnVendorDomain": true, "terms": "https://robolly.com/terms/", "privacy": "https://robolly.com/privacy/", "statusPage": "https://stats.uptimerobot.com/gpPQWiyqL", "changelog": "", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The terms (effective 8 April 2026) name Avantis Innovations LLC, Sheridan, Wyoming, under Wyoming law, and say Robolly is made by the team behind Sidemail.io and EmailSupportAI. The privacy policy has the same effective date.", "The terms contain no clause on automated access to the website that was found.", "robolly.com/robots.txt disallows /cdn-cgi/ only. api.robolly.com/robots.txt carries content-signal comments only. stats.uptimerobot.com/robots.txt disallows /api/, which the status page loads its data from, so no figures were read.", "RDAP gives robolly.com a registration date of 30 January 2021.", "/.well-known/security.txt answers 200 with the site's HTML shell, not a security.txt file. No changelog found." ], "score": 71 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/robolly.json", "live": { "slug": "robolly", "probe": { "target": "https://api.robolly.com/v1", "method": "get", "lastAt": "2026-11-07T19:22:30.107194019Z", "lastOk": true, "lastStatus": 404, "lastMs": 143, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 111, "p95ms24h": 182, "samples24h": 210, "samples30d": 210, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 197, "ok": 197 } ] }, "vendorStatus": { "page": "https://stats.uptimerobot.com/gpPQWiyqL", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:48:41.781150953Z" }, "securityTxt": { "url": "https://robolly.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:53.763302813Z" }, "llmsTxt": { "url": "https://robolly.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:50.184463404Z" }, "pages": [ { "url": "https://robolly.com/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:18:36.278744484Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8fd0121424f4" }, { "url": "https://robolly.com/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:18:38.520828166Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9c9ba532e790" } ], "mcpTools": { "url": "https://api.robolly.com/mcp", "checkedAt": "2026-11-07T01:47:28.870586301Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:47:28.870586301Z" }, "updatedAt": "2026-11-07T19:22:30.107194019Z" } }, "edges": [ { "by": 80, "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 changelog, release notes or dated API change was found. The sitemap marks every docs page as modified on 4 November 2026, which reads as a site rebuild rather than a change, so it isn't counted (0). No dated changes since 8 August (0). Support by email, with chat on higher plans; not tested (5 of 15). Not in the official MCP registry and no SDKs (0). No public package or repository (0). 0 + 0 + 5 + 0 + 0 = 5." }, "scores": { "a": 85, "b": 5 } }, { "by": 41, "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": "No OpenAPI or other machine-readable contract found for the REST API, and the MCP server is closed. The MCP page lists all nine tools and `get_template_modifications` returns each template's keys, constraints and examples at run time (8 of 25, on that partial evidence). llms.txt indexes the docs (10). The MCP page says what each tool does, which tools change templates or spend credits, and that there is no delete tool (14 of 20). Modification keys follow `{element-name}.{modification-key}` with constraints from the template rather than a fixed schema (7 of 15). Request examples throughout and an error code table with eight codes (13 of 15). /v1 paths with no changelog (5 of 15). 8 + 10 + 14 + 7 + 13 + 5 = 57." }, "scores": { "a": 98, "b": 57 } }, { "by": 22, "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 effective 8 April 2026 from Avantis Innovations LLC in Wyoming. The terms can change without notice (15). The privacy policy of the same date covers Google sign-in and Sheets data, says spreadsheet rows aren't kept beyond a render and account data is deleted with the account, and otherwise names no periods (10 of 30). No deprecation policy or notices (0). Hosting is described only as third-party vendors, with no processors or locations named, while the footer says Made in EU (2 of 20). 15 + 10 + 0 + 2 = 27." }, "scores": { "a": 71, "b": 49 } }, { "by": 10, "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": "Nine MCP tools (25). The renders list pages with a cursor, and templates are found by name (14 of 20). Errors carry `errorCode` and `developerMessage` with eight documented codes (17 of 20). Identical renders are cached for 45 days, so repeats are free and safe, the MCP server has no delete tool, and annotations couldn't be read on the closed server (12 of 20). Renders return the file synchronously by default, but there's no SDK (7 of 15). 25 + 14 + 17 + 12 + 7 = 75." }, "scores": { "a": 85, "b": 75 } }, { "by": 8, "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": "Bearer API key, signed render links, and MCP OAuth with one `robolly:mcp` scope limited to the organisation the user approves. Connections are listed and revoked under Connected AI Tools, and the API key is never shared with an OAuth client. No key scopes or rotation documented (22 of 30). The MCP server can create and update templates but not delete them; there's no read-only mode (10 of 20). Tools return the user's templates and public gallery designs (10 of 15). A renders list and the connected-tools view give some visibility, with no audit log documented (5 of 15). No security.txt (the path returns the site's HTML shell), disclosure policy, bug bounty or certification (0). 22 + 10 + 10 + 5 + 0 = 47." }, "scores": { "a": 55, "b": 47 } }, { "by": 7, "category": "reliability", "leads": "robolly", "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. The footer links an UptimeRobot status page, but it loads its figures from /api/, which stats.uptimerobot.com's robots.txt disallows, so the page showed no monitors or history (10 of 20 for a page that exists) and no history was read (5). A hard limit of 3 renders a second is published (15). The `rate-limit` error code and advice to send renders one at a time, and identical renders are cached for 45 days at no cost, which makes a retry safe; there's no Retry-After or backoff interval (8 of 15). No SLA found (0). The API isn't labelled beta (10). 10 + 5 + 15 + 8 + 0 + 10 = 48." }, "scores": { "a": 41, "b": 48 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Abyssale SAS", "b": "Avantis Innovations LLC (Robolly)", "name": "Vendor" }, { "a": "https://api.abyssale.com", "b": "https://api.robolly.com/v1", "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 Robolly terms of use (effective 8 April 2026)", "name": "Licence" }, { "a": "20", "b": "9", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "com.abyssale/mcp", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-29", "b": "none", "name": "Last release" }, { "a": "no date given", "b": "2026-04-08", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-04-08", "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": "not found in the text", "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": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" } ], "faq": [ { "answer": "Abyssale scores 65.6 (B) on agent readiness against Robolly's 48.4 (D), and leads in 5 of 7 scored categories. Robolly leads on reliability.", "question": "Which is better for AI agents, Abyssale or Robolly?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Abyssale and Robolly need an API key?" }, { "answer": "Yes. Abyssale has a hosted endpoint at https://api.abyssale.com and Robolly at https://api.robolly.com/v1.", "question": "Can an agent call Abyssale and Robolly without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 98 against 57", "Agent ergonomics, 85 against 75", "Security \u0026 auth, 55 against 47", "Maintenance \u0026 community, 85 against 5", "Transparency \u0026 trust, 71 against 49" ], "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": [ "Reliability, 48 against 41" ], "also": null, "goodFor": "Template-driven images, PDFs and short videos for marketers and developers who want a hosted editor and simple synchronous calls.", "slug": "robolly", "watchFor": "No OpenAPI or other machine-readable contract found" } ], "history": null, "job": { "capability": "design.render", "name": "Design rendering" }, "others": [ { "json": "https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-robolly.json", "title": "Adobe Photoshop API vs Robolly", "url": "https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-robolly" }, { "json": "https://www.anchorterminal.com/compare/apitemplate-io-vs-robolly.json", "title": "APITemplate.io vs Robolly", "url": "https://www.anchorterminal.com/compare/apitemplate-io-vs-robolly" }, { "json": "https://www.anchorterminal.com/compare/bannerbear-vs-robolly.json", "title": "Bannerbear API + MCP vs Robolly", "url": "https://www.anchorterminal.com/compare/bannerbear-vs-robolly" }, { "json": "https://www.anchorterminal.com/compare/canva-vs-robolly.json", "title": "Canva REST APIs + MCP vs Robolly", "url": "https://www.anchorterminal.com/compare/canva-vs-robolly" }, { "json": "https://www.anchorterminal.com/compare/contentdrips-vs-robolly.json", "title": "Contentdrips API and MCP vs Robolly", "url": "https://www.anchorterminal.com/compare/contentdrips-vs-robolly" }, { "json": "https://www.anchorterminal.com/compare/creatomate-vs-robolly.json", "title": "Creatomate vs Robolly", "url": "https://www.anchorterminal.com/compare/creatomate-vs-robolly" }, { "json": "https://www.anchorterminal.com/compare/dynapictures-vs-robolly.json", "title": "DynaPictures vs Robolly", "url": "https://www.anchorterminal.com/compare/dynapictures-vs-robolly" }, { "json": "https://www.anchorterminal.com/compare/layerre-vs-robolly.json", "title": "Layerre vs Robolly", "url": "https://www.anchorterminal.com/compare/layerre-vs-robolly" }, { "json": "https://www.anchorterminal.com/compare/photoroom-vs-robolly.json", "title": "Photoroom API vs Robolly", "url": "https://www.anchorterminal.com/compare/photoroom-vs-robolly" }, { "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/placid-vs-robolly.json", "title": "Placid API + MCP vs Robolly", "url": "https://www.anchorterminal.com/compare/placid-vs-robolly" }, { "json": "https://www.anchorterminal.com/compare/postnitro-vs-robolly.json", "title": "PostNitro vs Robolly", "url": "https://www.anchorterminal.com/compare/postnitro-vs-robolly" }, { "json": "https://www.anchorterminal.com/compare/robolly-vs-shotstack.json", "title": "Robolly vs Shotstack", "url": "https://www.anchorterminal.com/compare/robolly-vs-shotstack" }, { "json": "https://www.anchorterminal.com/compare/robolly-vs-templated.json", "title": "Robolly vs Templated API + MCP", "url": "https://www.anchorterminal.com/compare/robolly-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-pixelixe.json", "title": "Abyssale vs Pixelixe", "url": "https://www.anchorterminal.com/compare/abyssale-vs-pixelixe" }, { "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-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-robolly.json", "title": "Osmo CLI vs Robolly", "url": "https://www.anchorterminal.com/compare/osmo-cli-vs-robolly" }, { "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/abyssale-vs-photoroom.json", "title": "Abyssale vs Photoroom API", "url": "https://www.anchorterminal.com/compare/abyssale-vs-photoroom" } ], "panel": null, "scores": [ { "abyssale": 41, "by": 7, "edge": "robolly", "key": "reliability", "name": "Reliability", "robolly": 48, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "abyssale": 98, "by": 41, "edge": "abyssale", "key": "schema", "name": "Schema \u0026 documentation", "robolly": 57, "weight": 13 }, { "abyssale": 85, "by": 10, "edge": "abyssale", "key": "ergonomics", "name": "Agent ergonomics", "robolly": 75, "weight": 13 }, { "abyssale": 55, "by": 8, "edge": "abyssale", "key": "security", "name": "Security \u0026 auth", "robolly": 47, "weight": 14 }, { "abyssale": 35, "by": 0, "edge": "", "key": "payments", "name": "Payments \u0026 pricing", "robolly": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "abyssale": 85, "by": 80, "edge": "abyssale", "key": "maintenance", "name": "Maintenance \u0026 community", "robolly": 5, "weight": 7 }, { "abyssale": 71, "by": 22, "edge": "abyssale", "key": "transparency", "name": "Transparency \u0026 trust", "robolly": 49, "weight": 7 } ], "summary": "Abyssale scores 65.6 (B) on agent readiness against Robolly's 48.4 (D), and leads in 5 of 7 scored categories. Robolly leads on reliability. 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.", "robolly": "Robolly's nine MCP tools, synchronous renders, typed error codes and free cached re-renders keep template rendering cheap and predictable for an agent, and OAuth connections can be revoked per client. There is no OpenAPI file, changelog or dated release, and API access starts at $39 a month after a 7-day trial." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/abyssale-vs-robolly", "json": "https://www.anchorterminal.com/compare/abyssale-vs-robolly.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/abyssale-vs-robolly.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/abyssale-vs-robolly.min.md" }, "markdown": "Abyssale scores 65.6 (B) on agent readiness against Robolly's 48.4 (D), and leads in 5 of 7 scored categories. Robolly leads on reliability. 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- Robolly: grade D, 48.4/100, rank #1127 of 1510. Markdown https://www.anchorterminal.com/tools/robolly.md · JSON https://www.anchorterminal.com/api/v1/tools/robolly.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- Schema \u0026 documentation, 98 against 57\n- Agent ergonomics, 85 against 75\n- Security \u0026 auth, 55 against 47\n- Maintenance \u0026 community, 85 against 5\n- Transparency \u0026 trust, 71 against 49\n\nWatch for: API and MCP need the Pro plan at $45 a seat a month\n\n### Robolly (D)\n\nGood for: Template-driven images, PDFs and short videos for marketers and developers who want a hosted editor and simple synchronous calls.\n\nAhead on:\n- Reliability, 48 against 41\n\nWatch for: No OpenAPI or other machine-readable contract found\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Abyssale +80\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- Robolly (5): No changelog, release notes or dated API change was found. The sitemap marks every docs page as modified on 4 November 2026, which reads as a site rebuild rather than a change, so it isn't counted (0). No dated changes since 8 August (0). Support by email, with chat on higher plans; not tested (5 of 15). Not in the official MCP registry and no SDKs (0). No public package or repository (0). 0 + 0 + 5 + 0 + 0 = 5.\n\n### Schema \u0026 documentation: Abyssale +41\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- Robolly (57): No OpenAPI or other machine-readable contract found for the REST API, and the MCP server is closed. The MCP page lists all nine tools and `get_template_modifications` returns each template's keys, constraints and examples at run time (8 of 25, on that partial evidence). llms.txt indexes the docs (10). The MCP page says what each tool does, which tools change templates or spend credits, and that there is no delete tool (14 of 20). Modification keys follow `{element-name}.{modification-key}` with constraints from the template rather than a fixed schema (7 of 15). Request examples throughout and an error code table with eight codes (13 of 15). /v1 paths with no changelog (5 of 15). 8 + 10 + 14 + 7 + 13 + 5 = 57.\n\n### Transparency \u0026 trust: Abyssale +22\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- Robolly (49): Closed service under terms effective 8 April 2026 from Avantis Innovations LLC in Wyoming. The terms can change without notice (15). The privacy policy of the same date covers Google sign-in and Sheets data, says spreadsheet rows aren't kept beyond a render and account data is deleted with the account, and otherwise names no periods (10 of 30). No deprecation policy or notices (0). Hosting is described only as third-party vendors, with no processors or locations named, while the footer says Made in EU (2 of 20). 15 + 10 + 0 + 2 = 27.\n\n### Agent ergonomics: Abyssale +10\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- Robolly (75): Nine MCP tools (25). The renders list pages with a cursor, and templates are found by name (14 of 20). Errors carry `errorCode` and `developerMessage` with eight documented codes (17 of 20). Identical renders are cached for 45 days, so repeats are free and safe, the MCP server has no delete tool, and annotations couldn't be read on the closed server (12 of 20). Renders return the file synchronously by default, but there's no SDK (7 of 15). 25 + 14 + 17 + 12 + 7 = 75.\n\n### Security \u0026 auth: Abyssale +8\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- Robolly (47): Bearer API key, signed render links, and MCP OAuth with one `robolly:mcp` scope limited to the organisation the user approves. Connections are listed and revoked under Connected AI Tools, and the API key is never shared with an OAuth client. No key scopes or rotation documented (22 of 30). The MCP server can create and update templates but not delete them; there's no read-only mode (10 of 20). Tools return the user's templates and public gallery designs (10 of 15). A renders list and the connected-tools view give some visibility, with no audit log documented (5 of 15). No security.txt (the path returns the site's HTML shell), disclosure policy, bug bounty or certification (0). 22 + 10 + 10 + 5 + 0 = 47.\n\n### Reliability: Robolly +7\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- Robolly (48): Hosted lines. The footer links an UptimeRobot status page, but it loads its figures from /api/, which stats.uptimerobot.com's robots.txt disallows, so the page showed no monitors or history (10 of 20 for a page that exists) and no history was read (5). A hard limit of 3 renders a second is published (15). The `rate-limit` error code and advice to send renders one at a time, and identical renders are cached for 45 days at no cost, which makes a retry safe; there's no Retry-After or backoff interval (8 of 15). No SLA found (0). The API isn't labelled beta (10). 10 + 5 + 15 + 8 + 0 + 10 = 48.\n\n## Score by category\n\n| Category | Weight | Abyssale | Robolly | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 41 | 48 | Robolly +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 98 | 57 | Abyssale +41 |\n| Agent ergonomics | 13% (16.2 this run) | 85 | 75 | Abyssale +10 |\n| Security \u0026 auth | 14% (17.5 this run) | 55 | 47 | Abyssale +8 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 35 | 35 | even |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 85 | 5 | Abyssale +80 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 71 | 49 | Abyssale +22 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **65.6 · B** | **48.4 · D** | |\n\n## Facts side by side\n\n| Fact | Abyssale | Robolly |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Abyssale SAS | Avantis Innovations LLC (Robolly) |\n| Hosted endpoint | `https://api.abyssale.com` | `https://api.robolly.com/v1` |\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 Robolly terms of use (effective 8 April 2026) |\n| Tools exposed | 20 | 9 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `com.abyssale/mcp` | not listed |\n| Last release | 2026-10-29 | none |\n| Terms last updated | no date given | 2026-04-08 |\n| Privacy policy last updated | no date given | 2026-04-08 |\n| Customer content may train models | yes | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\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 | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\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**Robolly.** Robolly's nine MCP tools, synchronous renders, typed error codes and free cached re-renders keep template rendering cheap and predictable for an agent, and OAuth connections can be revoked per client. There is no OpenAPI file, changelog or dated release, and API access starts at $39 a month after a 7-day trial.\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### Robolly\n\n1. Call `get_template_modifications` before `render` to learn the keys a template accepts\n2. Send renders one at a time; the API refuses more than 3 a second with `rate-limit`\n3. Repeat an identical render freely; it is cached for 45 days and costs nothing\n4. Poll `get_render` after `render_video`, since video renders are queued\n5. Stop on `render-limit-exhausted` and tell the user the monthly credits are spent\n\n## Questions\n\n### Which is better for AI agents, Abyssale or Robolly?\n\nAbyssale scores 65.6 (B) on agent readiness against Robolly's 48.4 (D), and leads in 5 of 7 scored categories. Robolly leads on reliability.\n\n### Do Abyssale and Robolly need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Abyssale and Robolly without installing anything?\n\nYes. Abyssale has a hosted endpoint at https://api.abyssale.com and Robolly at https://api.robolly.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/abyssale-vs-robolly.json, and with the fewest tokens: https://www.anchorterminal.com/compare/abyssale-vs-robolly.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"abyssale\", \"b\": \"robolly\"}`. From a terminal: `anchor compare abyssale robolly`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/abyssale.json and https://www.anchorterminal.com/api/v1/tools/robolly.json\n\n## Other comparisons with Abyssale or Robolly\n\n- [Adobe Photoshop API vs Robolly](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-robolly.md)\n- [APITemplate.io vs Robolly](https://www.anchorterminal.com/compare/apitemplate-io-vs-robolly.md)\n- [Bannerbear API + MCP vs Robolly](https://www.anchorterminal.com/compare/bannerbear-vs-robolly.md)\n- [Canva REST APIs + MCP vs Robolly](https://www.anchorterminal.com/compare/canva-vs-robolly.md)\n- [Contentdrips API and MCP vs Robolly](https://www.anchorterminal.com/compare/contentdrips-vs-robolly.md)\n- [Creatomate vs Robolly](https://www.anchorterminal.com/compare/creatomate-vs-robolly.md)\n- [DynaPictures vs Robolly](https://www.anchorterminal.com/compare/dynapictures-vs-robolly.md)\n- [Layerre vs Robolly](https://www.anchorterminal.com/compare/layerre-vs-robolly.md)\n- [Photoroom API vs Robolly](https://www.anchorterminal.com/compare/photoroom-vs-robolly.md)\n- [Pixelixe vs Robolly](https://www.anchorterminal.com/compare/pixelixe-vs-robolly.md)\n- [Placid API + MCP vs Robolly](https://www.anchorterminal.com/compare/placid-vs-robolly.md)\n- [PostNitro vs Robolly](https://www.anchorterminal.com/compare/postnitro-vs-robolly.md)\n- [Robolly vs Shotstack](https://www.anchorterminal.com/compare/robolly-vs-shotstack.md)\n- [Robolly vs Templated API + MCP](https://www.anchorterminal.com/compare/robolly-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 Pixelixe](https://www.anchorterminal.com/compare/abyssale-vs-pixelixe.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 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 Robolly](https://www.anchorterminal.com/compare/osmo-cli-vs-robolly.md)\n- [Pictify vs Robolly](https://www.anchorterminal.com/compare/pictify-vs-robolly.md)\n- [Abyssale vs Photoroom API](https://www.anchorterminal.com/compare/abyssale-vs-photoroom.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 Robolly", "url": "" } ], "description": "Abyssale scores 65.6 (B) to Robolly's 48.4 (D) for design rendering. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Abyssale B 65.6", "Robolly D 48.4", "scores" ], "h1": "Abyssale vs Robolly", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/abyssale-vs-robolly", "published": "2026-10-01", "section": "tools", "title": "Abyssale vs Robolly for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/abyssale-vs-robolly" }, "tokens": { "markdown": 4600, "slim": 2780 }, "version": 1 }