{
  "data": {
    "a": {
      "slug": "clayzo",
      "name": "Clayzo",
      "vendor": "Clayzo",
      "vendorUrl": "https://www.clayzo.com",
      "company": "clayzo.com",
      "kind": "sdk",
      "category": "design-assets",
      "summary": "Clayzo is an animation engine and CLI for coding agents. Agents write animations as typed TypeScript documents, render frames to check them, and export video, GIF or SVG or play them live on the web and in Swift.",
      "url": "https://www.anchorterminal.com/tools/clayzo",
      "markdownUrl": "https://www.anchorterminal.com/tools/clayzo.md",
      "slimMarkdownUrl": "https://www.anchorterminal.com/tools/clayzo.min.md",
      "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/clayzo.json",
      "dns": "clayzo.grade.anchorterminal.com",
      "repo": "https://github.com/Clayzo/agent-skills",
      "transports": [
        "streamable-http"
      ],
      "remoteUrl": "https://app.clayzo.com/api/clayzo/mcp",
      "packages": [
        {
          "registry": "npm",
          "name": "clayzo"
        },
        {
          "registry": "npm",
          "name": "@clayzo/animation"
        },
        {
          "registry": "npm",
          "name": "@clayzo/webgl-player"
        }
      ],
      "auth": "mixed",
      "authNotes": "No account for `init`, authoring and playback. `preview`, `render-frame`, `review`, `package` and `export` need `npx clayzo login`, a device code approved in a browser. CI uses `CLAYZO_TOKEN` from `clayzo token create`, printed once and revocable. The Claude connector signs in with OAuth (scope `clayzo:author`).",
      "pricing": "free",
      "pricingNotes": "Free for animations on your own sites and apps, with a Clayzo sign-in. Building a product on Clayzo, such as an agent that generates animations for its users, needs a licence from team@clayzo.com. No price is published.",
      "priceSummary": "Free",
      "where": "hosted",
      "x402": {
        "level": "no",
        "evidence": "No x402, MPP or L402 in llms.txt, llms-full.txt, the docs or the plugin (checked 2026-11-18). Nothing is sold per use.",
        "endpoints": []
      },
      "toolCount": null,
      "popularity": {
        "githubStars": null,
        "npmWeekly": null,
        "pypiWeekly": null,
        "asOf": "2026-11-18"
      },
      "docsUrl": "https://docs.clayzo.com",
      "llmsTxt": "https://www.clayzo.com/llms.txt",
      "capabilities": [
        "design.render",
        "design.templates",
        "video.render"
      ],
      "tags": [
        "cli",
        "local",
        "closed-source",
        "free",
        "no-card",
        "agent-skills",
        "llms-txt",
        "remote-mcp",
        "oauth",
        "typescript",
        "ios",
        "macos",
        "video",
        "pre-1.0",
        "no-status-page"
      ],
      "lastRelease": "2026-11-17",
      "graded": true,
      "anchor": {
        "graded": true,
        "score": 50.9,
        "grade": "D",
        "agentReady": false,
        "rank": 1137,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 11,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 72,
          "maintenance": 58,
          "payments": 55,
          "reliability": 33,
          "schema": 57,
          "security": 52,
          "transparency": 26
        },
        "assessment": {
          "confidence": "low",
          "date": "2026-11-18"
        },
        "negative": 0,
        "verdict": "Agents get a CLI that returns JSON, coded errors, frame and contact-sheet renders to check their own work, and skills that load references on demand, free for a user's own sites. Rendering and export need a browser sign-in, the source and licence are closed, and the terms and privacy policy render only in a browser.",
        "bestFor": "Coding agents that make motion graphics, product animations or interactive web animations for a user's own site or app.",
        "strengths": [
          "Every command prints JSON on stdout, with errors as JSON objects carrying a `code` such as `CLAYZO_AUTH_REQUIRED`",
          "`render-frame` renders one frame, a labelled contact sheet or the loop seam, so an agent can check motion before a person looks",
          "Exports MP4, MOV, WebM, WebP, GIF, PNG sequences, SVG and portable `.clayzo` bundles, rendered locally",
          "CI tokens are printed once, stored as a hash, and can be listed and revoked from the CLI",
          "Releases 0.3.7 to 0.3.23 shipped between 27 September and 17 November 2026"
        ],
        "weaknesses": [
          "`preview`, `render-frame`, `review`, `package` and `export` need a Clayzo sign-in approved in a browser",
          "Closed source under a proprietary licence (`LicenseRef-Clayzo-SDK-License`), with no public CI, tests or issue tracker for the CLI",
          "The terms and privacy policy render only in a browser and couldn't be read. No company details were found on readable pages",
          "Building a product on Clayzo needs a licence negotiated by email, with no published price",
          "No changelog. Versions are visible only in package and skills metadata"
        ],
        "agentNotes": [
          "Run `npx clayzo doctor --json` first to see sign-in state and whether an update is required",
          "If a command returns `CLAYZO_AUTH_REQUIRED`, ask the user to run `npx clayzo login` and approve the device in a browser",
          "In CI, set `CLAYZO_TOKEN` to a token from `clayzo token create`, since the browser sign-in isn't available there",
          "Treat exit code 2 as 'update required' and run `clayzo update` before retrying protected commands",
          "Check frames with `render-frame` and `--max-dimension` before a full export to keep renders small"
        ],
        "metrics": {
          "kind": "local",
          "measured": false
        },
        "reviewCount": 0,
        "avgRating": 0,
        "history": [
          {
            "basis": "public evidence",
            "confidence": "low",
            "grade": "D",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 50.9
          }
        ],
        "editorialScores": {
          "ergonomics": 72,
          "maintenance": 58,
          "payments": 55,
          "reliability": 33,
          "schema": 57,
          "security": 52,
          "transparency": 19
        },
        "provenanceScore": 32,
        "checked": {
          "categories": {
            "ergonomics": "2026-11-18",
            "maintenance": "2026-11-18",
            "payments": "2026-11-18",
            "reliability": "2026-11-18",
            "schema": "2026-11-18",
            "security": "2026-11-18",
            "transparency": "2026-11-18"
          },
          "last": "2026-11-18",
          "oldest": "2026-11-18",
          "stale": false,
          "staleAfterDays": 90
        }
      },
      "connect": {
        "install": "npx clayzo@latest init",
        "headless": {
          "command": "npx clayzo export animations/hero.json hero.mp4 --format mp4 --tier final",
          "env": {
            "CLAYZO_TOKEN": "\u003ctoken from clayzo token create\u003e"
          }
        }
      },
      "letme": {
        "capability": "https://letme.dev/design.render",
        "tool": "https://letme.dev/clayzo"
      },
      "area": "design-diagrams",
      "provenance": {
        "legalEntity": "",
        "domain": "clayzo.com",
        "domainRegistered": "",
        "endpointOnVendorDomain": true,
        "terms": "https://clayzo.com/terms",
        "privacy": "https://clayzo.com/privacy",
        "statusPage": "",
        "changelog": "",
        "securityTxt": "none",
        "checked": "2026-11-18",
        "notes": [
          "clayzo.com/terms and /privacy are linked from the Claude plugin manifest and listed in the sitemap (lastmod 27 September and 4 October 2026), but render only in a browser. Our reader got the home page's text, so neither was read.",
          "The blog post of 27 September 2026 is signed 'Clayzo Labs'. No legal entity, address or registration was found on readable pages.",
          "clayzo.com/robots.txt allows all agents with Content-Signal ai-train=yes, search=yes, ai-input=yes, and points agents to llms.txt and Markdown pages. docs.clayzo.com allows all but /_next/ and /cdn-cgi/. app.clayzo.com/robots.txt answers 404 (no rules).",
          "/.well-known/security.txt returns the home page, so there is none. No status page found."
        ],
        "score": 32
      },
      "pageJsonUrl": "https://www.anchorterminal.com/tools/clayzo.json",
      "live": {
        "slug": "clayzo",
        "probe": {
          "target": "https://app.clayzo.com/api/clayzo/mcp",
          "method": "mcp-initialize",
          "lastAt": "2026-11-18T22:43:14.35017681Z",
          "lastOk": true,
          "lastStatus": 401,
          "lastMs": 251,
          "lastNote": "asks for credentials",
          "authRequired": true,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 352,
          "p95ms24h": 1232,
          "samples24h": 11,
          "samples30d": 11,
          "days": [
            {
              "date": "2026-11-18",
              "probes": 11,
              "ok": 11
            }
          ],
          "since": "2026-11-18T21:37:48.310863822Z"
        },
        "updatedAt": "2026-11-18T22:43:14.35017681Z"
      },
      "streak": {
        "days": 0,
        "from": "2026-11-18",
        "sinceWatching": true,
        "best": 0
      }
    },
    "answer": "Clayzo scores 50.9 (D) on agent readiness against Pixelixe's 39.2 (E), and leads in 5 of 7 scored categories. Pixelixe leads on schema \u0026 documentation and transparency \u0026 trust.",
    "b": {
      "slug": "pixelixe",
      "name": "Pixelixe",
      "vendor": "Pixelixe",
      "vendorUrl": "https://pixelixe.com",
      "company": "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": 39.2,
        "grade": "E",
        "agentReady": false,
        "rank": 1397,
        "ranked": true,
        "rankOf": 1557,
        "categoryRank": 16,
        "methodology": "1.0",
        "run": "2026-10-01",
        "scores": {
          "ergonomics": 49,
          "maintenance": 19,
          "payments": 45,
          "reliability": 15,
          "schema": 66,
          "security": 38,
          "transparency": 41
        },
        "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": "E",
            "methodology": "1.0",
            "run": "2026-10-01",
            "runLabel": "October 2026 research run",
            "score": 39.2
          }
        ],
        "editorialScores": {
          "ergonomics": 49,
          "maintenance": 19,
          "payments": 45,
          "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",
          "lastMoved": "2026-11-13",
          "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-18T22:43:51.772556521Z",
          "lastOk": true,
          "lastStatus": 404,
          "lastMs": 188,
          "authRequired": false,
          "uptime24h": 100,
          "uptime30d": 100,
          "p50ms24h": 31,
          "p95ms24h": 151,
          "samples24h": 241,
          "samples30d": 2913,
          "days": [
            {
              "date": "2026-11-06",
              "probes": 13,
              "ok": 13
            },
            {
              "date": "2026-11-07",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-08",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-09",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-10",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-11",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-12",
              "probes": 245,
              "ok": 245
            },
            {
              "date": "2026-11-13",
              "probes": 238,
              "ok": 238
            },
            {
              "date": "2026-11-14",
              "probes": 244,
              "ok": 244
            },
            {
              "date": "2026-11-15",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-16",
              "probes": 243,
              "ok": 243
            },
            {
              "date": "2026-11-17",
              "probes": 242,
              "ok": 242
            },
            {
              "date": "2026-11-18",
              "probes": 228,
              "ok": 228
            }
          ],
          "since": "2026-11-06T00:00:00Z"
        },
        "versions": [
          {
            "registry": "mcp-registry",
            "name": "com.pixelixe/pixelixe-mcp",
            "version": "1.0.2",
            "seenAt": "2026-11-18T22:45:57.054523297Z"
          }
        ],
        "securityTxt": {
          "url": "https://pixelixe.com/.well-known/security.txt",
          "state": "none",
          "checkedAt": "2026-11-18T16:29:52.241862615Z"
        },
        "llmsTxt": {
          "url": "https://pixelixe.com/llms.txt",
          "ok": true,
          "status": 200,
          "checkedAt": "2026-11-18T16:15:46.093112537Z"
        },
        "domain": {
          "domain": "pixelixe.com",
          "registered": "2018-09-17",
          "source": "https://rdap.verisign.com/com/v1/domain/pixelixe.com",
          "checkedAt": "2026-11-15T15:14:26.032519624Z"
        },
        "pages": [
          {
            "url": "https://pixelixe.com/privacy-policy.html",
            "kind": "privacy",
            "status": 304,
            "checkedAt": "2026-11-18T21:50:35.857795619Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "832cb532d5ba"
          },
          {
            "url": "https://pixelixe.com/terms.html",
            "kind": "terms",
            "status": 304,
            "checkedAt": "2026-11-18T21:50:38.059085025Z",
            "changedAt": "0001-01-01T00:00:00Z",
            "fingerprint": "764ac1d560a1"
          }
        ],
        "mcpTools": {
          "url": "https://studio.pixelixe.com/api/mcp/v1",
          "checkedAt": "2026-11-18T04:27:16.858159417Z",
          "status": "auth",
          "note": "asks for credentials before listing its tools",
          "changedAt": "2026-11-07T01:46:51.581135972Z"
        },
        "updatedAt": "2026-11-18T22:45:57.054523297Z"
      },
      "streak": {
        "days": 12,
        "from": "2026-11-06",
        "sinceWatching": true,
        "best": 12
      }
    },
    "edges": [
      {
        "by": 39,
        "category": "maintenance",
        "leads": "clayzo",
        "name": "Maintenance \u0026 community",
        "reasons": {
          "a": "Version 0.3.23 of the CLI, packages, skills and Claude plugin was released on 17 November 2026, one day before this check (30). All 22 releases from 0.3.1 (24 August 2026) to 0.3.23 fall in the 90 days, per the skills repository's release commits (20). No public issue tracker. The docs repository's merge commits run to pull request #15, and support is an email address (5 of 25). Not in the official MCP registry (searched for clayzo on 18 November 2026) (0). No public CI or dependency information for the closed packages (3 of 10). 30+20+5+0+3 = 58.",
          "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": 58,
          "b": 19
        }
      },
      {
        "by": 23,
        "category": "ergonomics",
        "leads": "clayzo",
        "name": "Agent ergonomics",
        "reasons": {
          "a": "Two skills whose top-level router files stay short, with references loaded only when a request needs them, per the skills README (22 of 25). `--max-dimension` bounds a render, `render-frame` picks one frame, a sheet or the loop seam, and time options are in ticks for exact ranges (14 of 20). JSON errors with a `code`, progress on stderr so stdout stays parseable, and documented exit codes (14 of 20). Renders and exports are local and repeatable. No MCP annotations or idempotency keys could be read (10 of 20). `init --yes` takes defaults without prompting. Packages for TypeScript on the web and a Swift player for iOS and macOS (12 of 15). 22+14+14+10+12 = 72.",
          "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": 72,
          "b": 49
        }
      },
      {
        "by": 18,
        "category": "reliability",
        "leads": "clayzo",
        "name": "Reliability",
        "reasons": {
          "a": "Read with the local-package lines, since the CLI renders on the owner's machine. `clayzo`, `@clayzo/animation` and `@clayzo/webgl-player` install from npm with Node.js 22.13 or newer stated, and the initialiser documents its flags and fallbacks (20). The CLI source is closed and the public repositories (docs, skills, Claude plugin) have no CI workflows (0). No public issue tracker for the CLI was found. Support is team@clayzo.com (5 of 25). Versions follow a 0.3.x pattern and the CLI refuses protected commands with exit code 2 when it's below the service's minimum, but there is no changelog naming breaking changes (3 of 15). Version 0.3.23 is below 1.0, though the skills release file labels the channel 'stable' (5 of 15). Protected commands also depend on Clayzo's sign-in service, which has no status page. 20+0+5+3+5 = 33.",
          "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": 33,
          "b": 15
        }
      },
      {
        "by": 15,
        "category": "transparency",
        "leads": "pixelixe",
        "name": "Transparency \u0026 trust",
        "reasons": {
          "a": "Closed source. The npm packages say 'SEE LICENSE IN LICENSE.md' and the Claude plugin names `LicenseRef-Clayzo-SDK-License`, but the licence text wasn't read. clayzo.com/terms and /privacy, linked from the plugin manifest and listed in the sitemap (27 September and 4 October 2026), render only in a browser and returned the home page's text to our reader (5 of 30). The docs say playback makes no request to Clayzo and the connector sends no animations or exports to Clayzo, but there is no readable privacy policy (8 of 30). The CLI enforces a minimum version, with no deprecation policy (3 of 20). Update checks can be turned off with `NO_UPDATE_NOTIFIER`. No other telemetry statement was found (3 of 20). 5+8+3+3 = 19.",
          "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": 26,
          "b": 41
        }
      },
      {
        "by": 14,
        "category": "security",
        "leads": "clayzo",
        "name": "Security \u0026 auth",
        "reasons": {
          "a": "Device sign-in through the browser with locally stored, refreshed credentials, `logout` that revokes the device, and CI tokens printed once, stored as a hash, listed and revoked by id. The MCP connector uses OAuth with the `clayzo:author` scope. No scopes on CI tokens are documented (26 of 30). The CLI writes only local files and the connector only signs the CLI in, so there are no remote destructive actions, but there is no read-only mode (12 of 20). The tool returns rendered frames of the agent's own documents, not untrusted content (10). `token list` shows names, prefixes and status, with no audit log (4 of 15). No security.txt (the address returns the home page), disclosure policy or certification found on readable pages (0 of 20). 26+12+10+4+0 = 52.",
          "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": 52,
          "b": 38
        }
      },
      {
        "by": 10,
        "category": "payments",
        "leads": "clayzo",
        "name": "Payments \u0026 pricing",
        "reasons": {
          "a": "Read as a free package with a hosted sign-in, since nothing is sold for a user's own sites. No x402, MPP or L402 (0). The price is stated publicly as free for animations on your own sites and apps, while a product built on Clayzo needs a licence by email with no price (20 of 30). Free with a sign-in, no card mentioned anywhere read (30). A person approves the device in a browser before any protected command. After that a CI token can be created from the CLI, a programmatic route after a human sign-in (5 of 30). 0+20+30+5 = 55.",
          "b": "No x402, MPP or L402 (0). Plan prices with monthly document counts are public, with no per-image price (10). 10-day trial with no card (20). A person signs up and copies the key, or approves OAuth in a browser (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45."
        },
        "scores": {
          "a": 55,
          "b": 45
        }
      }
    ],
    "facts": [
      {
        "a": "SDK + MCP",
        "b": "HTTP API",
        "name": "Kind"
      },
      {
        "a": "Clayzo",
        "b": "Pixelixe",
        "name": "Vendor"
      },
      {
        "a": "https://app.clayzo.com/api/clayzo/mcp",
        "b": "https://studio.pixelixe.com/api",
        "name": "Hosted endpoint"
      },
      {
        "a": "Streamable HTTP",
        "b": "HTTP, Streamable HTTP",
        "name": "Transports"
      },
      {
        "a": "OAuth or key",
        "b": "OAuth or key",
        "name": "Auth"
      },
      {
        "a": "Free",
        "b": "Paid",
        "name": "Pricing"
      },
      {
        "a": "no",
        "b": "no",
        "name": "x402"
      },
      {
        "a": "none",
        "b": "Closed service under the Pixelixe terms of service (last modified 19 March 2026)",
        "name": "Licence"
      },
      {
        "a": "none",
        "b": "7",
        "name": "Tools exposed"
      },
      {
        "a": "no",
        "b": "no",
        "name": "Read-only variant documented"
      },
      {
        "a": "yes",
        "b": "yes",
        "name": "llms.txt"
      },
      {
        "a": "not listed",
        "b": "com.pixelixe/pixelixe-mcp",
        "name": "MCP registry"
      },
      {
        "a": "2026-11-17",
        "b": "2026-03-26",
        "name": "Last release"
      },
      {
        "a": "couldn't be read",
        "b": "2026-03-19",
        "name": "Terms last updated"
      },
      {
        "a": "couldn't be read",
        "b": "2026-04-07",
        "name": "Privacy policy last updated"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Customer content may train models"
      },
      {
        "a": "couldn't be read",
        "b": "yes",
        "name": "Terms restrict automated access"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Terms restrict benchmarking"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Terms or service can change without notice"
      },
      {
        "a": "couldn't be read",
        "b": "not found in the text",
        "name": "Arbitration or class-action waiver"
      }
    ],
    "faq": [
      {
        "answer": "Clayzo scores 50.9 (D) on agent readiness against Pixelixe's 39.2 (E), and leads in 5 of 7 scored categories. Pixelixe leads on schema \u0026 documentation and transparency \u0026 trust.",
        "question": "Which is better for AI agents, Clayzo or Pixelixe?"
      },
      {
        "answer": "Yes. Clayzo has a hosted endpoint at https://app.clayzo.com/api/clayzo/mcp and Pixelixe at https://studio.pixelixe.com/api.",
        "question": "Can an agent call Clayzo and Pixelixe without installing anything?"
      }
    ],
    "goodFor": [
      {
        "aheadOn": [
          "Reliability, 33 against 15",
          "Agent ergonomics, 72 against 49",
          "Security \u0026 auth, 52 against 38",
          "Payments \u0026 pricing, 55 against 45",
          "Maintenance \u0026 community, 58 against 19"
        ],
        "also": null,
        "goodFor": "Coding agents that make motion graphics, product animations or interactive web animations for a user's own site or app.",
        "slug": "clayzo",
        "watchFor": "`preview`, `render-frame`, `review`, `package` and `export` need a Clayzo sign-in approved in a browser"
      },
      {
        "aheadOn": [
          "Schema \u0026 documentation, 66 against 57",
          "Transparency \u0026 trust, 41 against 26"
        ],
        "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": {
      "clayzo": null,
      "pixelixe": [
        {
          "causes": [
            "method"
          ],
          "date": "2026-11-13",
          "delta": 1.9,
          "from": 37.3,
          "fromGrade": "F",
          "to": 39.2,
          "toGrade": "E"
        }
      ]
    },
    "job": {
      "capability": "design.render",
      "name": "Design rendering"
    },
    "others": [
      {
        "json": "https://www.anchorterminal.com/compare/apitemplate-io-vs-clayzo.json",
        "title": "APITemplate.io vs Clayzo",
        "url": "https://www.anchorterminal.com/compare/apitemplate-io-vs-clayzo"
      },
      {
        "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-clayzo.json",
        "title": "Bannerbear API + MCP vs Clayzo",
        "url": "https://www.anchorterminal.com/compare/bannerbear-vs-clayzo"
      },
      {
        "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-clayzo.json",
        "title": "Canva REST APIs + MCP vs Clayzo",
        "url": "https://www.anchorterminal.com/compare/canva-vs-clayzo"
      },
      {
        "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/clayzo-vs-photoroom.json",
        "title": "Clayzo vs Photoroom API",
        "url": "https://www.anchorterminal.com/compare/clayzo-vs-photoroom"
      },
      {
        "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-clayzo.json",
        "title": "Abyssale vs Clayzo",
        "url": "https://www.anchorterminal.com/compare/abyssale-vs-clayzo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/abyssale-vs-pixelixe.json",
        "title": "Abyssale vs Pixelixe",
        "url": "https://www.anchorterminal.com/compare/abyssale-vs-pixelixe"
      },
      {
        "json": "https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-clayzo.json",
        "title": "Adobe Photoshop API vs Clayzo",
        "url": "https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-clayzo"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clayzo-vs-contentdrips.json",
        "title": "Clayzo vs Contentdrips API and MCP",
        "url": "https://www.anchorterminal.com/compare/clayzo-vs-contentdrips"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clayzo-vs-creatomate.json",
        "title": "Clayzo vs Creatomate",
        "url": "https://www.anchorterminal.com/compare/clayzo-vs-creatomate"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clayzo-vs-dynapictures.json",
        "title": "Clayzo vs DynaPictures",
        "url": "https://www.anchorterminal.com/compare/clayzo-vs-dynapictures"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clayzo-vs-layerre.json",
        "title": "Clayzo vs Layerre",
        "url": "https://www.anchorterminal.com/compare/clayzo-vs-layerre"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clayzo-vs-osmo-cli.json",
        "title": "Clayzo vs Osmo CLI",
        "url": "https://www.anchorterminal.com/compare/clayzo-vs-osmo-cli"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clayzo-vs-pictify.json",
        "title": "Clayzo vs Pictify",
        "url": "https://www.anchorterminal.com/compare/clayzo-vs-pictify"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clayzo-vs-placid.json",
        "title": "Clayzo vs Placid API + MCP",
        "url": "https://www.anchorterminal.com/compare/clayzo-vs-placid"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clayzo-vs-postnitro.json",
        "title": "Clayzo vs PostNitro",
        "url": "https://www.anchorterminal.com/compare/clayzo-vs-postnitro"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clayzo-vs-robolly.json",
        "title": "Clayzo vs Robolly",
        "url": "https://www.anchorterminal.com/compare/clayzo-vs-robolly"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clayzo-vs-shotstack.json",
        "title": "Clayzo vs Shotstack",
        "url": "https://www.anchorterminal.com/compare/clayzo-vs-shotstack"
      },
      {
        "json": "https://www.anchorterminal.com/compare/clayzo-vs-templated.json",
        "title": "Clayzo vs Templated API + MCP",
        "url": "https://www.anchorterminal.com/compare/clayzo-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/adobe-photoshop-api-vs-pixelixe.json",
        "title": "Adobe Photoshop API vs Pixelixe",
        "url": "https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-pixelixe"
      },
      {
        "json": "https://www.anchorterminal.com/compare/photoroom-vs-pixelixe.json",
        "title": "Photoroom API vs Pixelixe",
        "url": "https://www.anchorterminal.com/compare/photoroom-vs-pixelixe"
      }
    ],
    "panel": null,
    "scores": [
      {
        "by": 18,
        "clayzo": 33,
        "edge": "clayzo",
        "key": "reliability",
        "name": "Reliability",
        "pixelixe": 15,
        "weight": 16
      },
      {
        "key": "performance",
        "name": "Performance",
        "pending": true,
        "weight": 10
      },
      {
        "by": 9,
        "clayzo": 57,
        "edge": "pixelixe",
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "pixelixe": 66,
        "weight": 13
      },
      {
        "by": 23,
        "clayzo": 72,
        "edge": "clayzo",
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "pixelixe": 49,
        "weight": 13
      },
      {
        "by": 14,
        "clayzo": 52,
        "edge": "clayzo",
        "key": "security",
        "name": "Security \u0026 auth",
        "pixelixe": 38,
        "weight": 14
      },
      {
        "by": 10,
        "clayzo": 55,
        "edge": "clayzo",
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "pixelixe": 45,
        "weight": 10
      },
      {
        "key": "tasks",
        "name": "Task success",
        "pending": true,
        "weight": 10
      },
      {
        "by": 39,
        "clayzo": 58,
        "edge": "clayzo",
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "pixelixe": 19,
        "weight": 7
      },
      {
        "by": 15,
        "clayzo": 26,
        "edge": "pixelixe",
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "pixelixe": 41,
        "weight": 7
      }
    ],
    "summary": "Clayzo scores 50.9 (D) on agent readiness against Pixelixe's 39.2 (E), and leads in 5 of 7 scored categories. Pixelixe leads on schema \u0026 documentation and transparency \u0026 trust. Both do design rendering.",
    "tasks": null,
    "tutorials": [],
    "verdicts": {
      "clayzo": "Agents get a CLI that returns JSON, coded errors, frame and contact-sheet renders to check their own work, and skills that load references on demand, free for a user's own sites. Rendering and export need a browser sign-in, the source and licence are closed, and the terms and privacy policy render only in a browser.",
      "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/clayzo-vs-pixelixe",
    "json": "https://www.anchorterminal.com/compare/clayzo-vs-pixelixe.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/compare/clayzo-vs-pixelixe.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/compare/clayzo-vs-pixelixe.min.md"
  },
  "markdown": "Clayzo scores 50.9 (D) on agent readiness against Pixelixe's 39.2 (E), and leads in 5 of 7 scored categories. Pixelixe leads on schema \u0026 documentation and transparency \u0026 trust. Both do design rendering.\n\n- Clayzo: grade D, 50.9/100, rank #1137 of 1557. Markdown https://www.anchorterminal.com/tools/clayzo.md · JSON https://www.anchorterminal.com/api/v1/tools/clayzo.json\n- Pixelixe: grade E, 39.2/100, rank #1397 of 1557. 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 171 assets comparisons: https://www.anchorterminal.com/compare/design-assets/index.md\n\n## Which one, for what\n\n### Clayzo (D)\n\nGood for: Coding agents that make motion graphics, product animations or interactive web animations for a user's own site or app.\n\nAhead on:\n- Reliability, 33 against 15\n- Agent ergonomics, 72 against 49\n- Security \u0026 auth, 52 against 38\n- Payments \u0026 pricing, 55 against 45\n- Maintenance \u0026 community, 58 against 19\n\nWatch for: `preview`, `render-frame`, `review`, `package` and `export` need a Clayzo sign-in approved in a browser\n\n### Pixelixe (E)\n\nGood for: Template fills and white-label editing for marketing and SaaS teams, with a JSON-to-graphic route for agents.\n\nAhead on:\n- Schema \u0026 documentation, 66 against 57\n- Transparency \u0026 trust, 41 against 26\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: Clayzo +39\n\n- Clayzo (58): Version 0.3.23 of the CLI, packages, skills and Claude plugin was released on 17 November 2026, one day before this check (30). All 22 releases from 0.3.1 (24 August 2026) to 0.3.23 fall in the 90 days, per the skills repository's release commits (20). No public issue tracker. The docs repository's merge commits run to pull request #15, and support is an email address (5 of 25). Not in the official MCP registry (searched for clayzo on 18 November 2026) (0). No public CI or dependency information for the closed packages (3 of 10). 30+20+5+0+3 = 58.\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: Clayzo +23\n\n- Clayzo (72): Two skills whose top-level router files stay short, with references loaded only when a request needs them, per the skills README (22 of 25). `--max-dimension` bounds a render, `render-frame` picks one frame, a sheet or the loop seam, and time options are in ticks for exact ranges (14 of 20). JSON errors with a `code`, progress on stderr so stdout stays parseable, and documented exit codes (14 of 20). Renders and exports are local and repeatable. No MCP annotations or idempotency keys could be read (10 of 20). `init --yes` takes defaults without prompting. Packages for TypeScript on the web and a Swift player for iOS and macOS (12 of 15). 22+14+14+10+12 = 72.\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### Reliability: Clayzo +18\n\n- Clayzo (33): Read with the local-package lines, since the CLI renders on the owner's machine. `clayzo`, `@clayzo/animation` and `@clayzo/webgl-player` install from npm with Node.js 22.13 or newer stated, and the initialiser documents its flags and fallbacks (20). The CLI source is closed and the public repositories (docs, skills, Claude plugin) have no CI workflows (0). No public issue tracker for the CLI was found. Support is team@clayzo.com (5 of 25). Versions follow a 0.3.x pattern and the CLI refuses protected commands with exit code 2 when it's below the service's minimum, but there is no changelog naming breaking changes (3 of 15). Version 0.3.23 is below 1.0, though the skills release file labels the channel 'stable' (5 of 15). Protected commands also depend on Clayzo's sign-in service, which has no status page. 20+0+5+3+5 = 33.\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### Transparency \u0026 trust: Pixelixe +15\n\n- Clayzo (26): Closed source. The npm packages say 'SEE LICENSE IN LICENSE.md' and the Claude plugin names `LicenseRef-Clayzo-SDK-License`, but the licence text wasn't read. clayzo.com/terms and /privacy, linked from the plugin manifest and listed in the sitemap (27 September and 4 October 2026), render only in a browser and returned the home page's text to our reader (5 of 30). The docs say playback makes no request to Clayzo and the connector sends no animations or exports to Clayzo, but there is no readable privacy policy (8 of 30). The CLI enforces a minimum version, with no deprecation policy (3 of 20). Update checks can be turned off with `NO_UPDATE_NOTIFIER`. No other telemetry statement was found (3 of 20). 5+8+3+3 = 19.\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### Security \u0026 auth: Clayzo +14\n\n- Clayzo (52): Device sign-in through the browser with locally stored, refreshed credentials, `logout` that revokes the device, and CI tokens printed once, stored as a hash, listed and revoked by id. The MCP connector uses OAuth with the `clayzo:author` scope. No scopes on CI tokens are documented (26 of 30). The CLI writes only local files and the connector only signs the CLI in, so there are no remote destructive actions, but there is no read-only mode (12 of 20). The tool returns rendered frames of the agent's own documents, not untrusted content (10). `token list` shows names, prefixes and status, with no audit log (4 of 15). No security.txt (the address returns the home page), disclosure policy or certification found on readable pages (0 of 20). 26+12+10+4+0 = 52.\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### Payments \u0026 pricing: Clayzo +10\n\n- Clayzo (55): Read as a free package with a hosted sign-in, since nothing is sold for a user's own sites. No x402, MPP or L402 (0). The price is stated publicly as free for animations on your own sites and apps, while a product built on Clayzo needs a licence by email with no price (20 of 30). Free with a sign-in, no card mentioned anywhere read (30). A person approves the device in a browser before any protected command. After that a CI token can be created from the CLI, a programmatic route after a human sign-in (5 of 30). 0+20+30+5 = 55.\n- Pixelixe (45): No x402, MPP or L402 (0). Plan prices with monthly document counts are public, with no per-image price (10). 10-day trial with no card (20). A person signs up and copies the key, or approves OAuth in a browser (0). 0 + 10 + 20 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.\n\n## Score by category\n\n| Category | Weight | Clayzo | Pixelixe | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 33 | 15 | Clayzo +18 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% | 57 | 66 | Pixelixe +9 |\n| Agent ergonomics | 13% | 72 | 49 | Clayzo +23 |\n| Security \u0026 auth | 14% | 52 | 38 | Clayzo +14 |\n| Payments \u0026 pricing | 10% | 55 | 45 | Clayzo +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% | 58 | 19 | Clayzo +39 |\n| Transparency \u0026 trust | 7% | 26 | 41 | Pixelixe +15 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **50.9 · D** | **39.2 · E** | |\n\n## Facts side by side\n\n| Fact | Clayzo | Pixelixe |\n| --- | --- | --- |\n| Kind | SDK + MCP | HTTP API |\n| Vendor | Clayzo | Pixelixe |\n| Hosted endpoint | `https://app.clayzo.com/api/clayzo/mcp` | `https://studio.pixelixe.com/api` |\n| Transports | Streamable HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Free | Paid |\n| x402 | no | no |\n| Licence | none | Closed service under the Pixelixe terms of service (last modified 19 March 2026) |\n| Tools exposed | none | 7 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | not listed | `com.pixelixe/pixelixe-mcp` |\n| Last release | 2026-11-17 | 2026-03-26 |\n| Terms last updated | couldn't be read | 2026-03-19 |\n| Privacy policy last updated | couldn't be read | 2026-04-07 |\n| Customer content may train models | couldn't be read | not found in the text |\n| Terms restrict automated access | couldn't be read | yes |\n| Terms restrict benchmarking | couldn't be read | not found in the text |\n| Terms or service can change without notice | couldn't be read | not found in the text |\n| Arbitration or class-action waiver | couldn't be read | not found in the text |\n\n## How the scores have moved\n\n### Clayzo\n\nNo score change since it was listed.\n\n### Pixelixe\n\n- +1.9 on 13 November 2026 (F to E): checklist\n\n## Verdicts\n\n**Clayzo.** Agents get a CLI that returns JSON, coded errors, frame and contact-sheet renders to check their own work, and skills that load references on demand, free for a user's own sites. Rendering and export need a browser sign-in, the source and licence are closed, and the terms and privacy policy render only in a browser.\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### Clayzo\n\n1. Run `npx clayzo doctor --json` first to see sign-in state and whether an update is required\n2. If a command returns `CLAYZO_AUTH_REQUIRED`, ask the user to run `npx clayzo login` and approve the device in a browser\n3. In CI, set `CLAYZO_TOKEN` to a token from `clayzo token create`, since the browser sign-in isn't available there\n4. Treat exit code 2 as 'update required' and run `clayzo update` before retrying protected commands\n5. Check frames with `render-frame` and `--max-dimension` before a full export to keep renders small\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, Clayzo or Pixelixe?\n\nClayzo scores 50.9 (D) on agent readiness against Pixelixe's 39.2 (E), and leads in 5 of 7 scored categories. Pixelixe leads on schema \u0026 documentation and transparency \u0026 trust.\n\n### Can an agent call Clayzo and Pixelixe without installing anything?\n\nYes. Clayzo has a hosted endpoint at https://app.clayzo.com/api/clayzo/mcp and Pixelixe at https://studio.pixelixe.com/api.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/clayzo-vs-pixelixe.json, and with the fewest tokens: https://www.anchorterminal.com/compare/clayzo-vs-pixelixe.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"clayzo\", \"b\": \"pixelixe\"}`. From a terminal: `anchor compare clayzo pixelixe`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/clayzo.json and https://www.anchorterminal.com/api/v1/tools/pixelixe.json\n\n## Other comparisons with Clayzo or Pixelixe\n\n- [APITemplate.io vs Clayzo](https://www.anchorterminal.com/compare/apitemplate-io-vs-clayzo.md)\n- [APITemplate.io vs Pixelixe](https://www.anchorterminal.com/compare/apitemplate-io-vs-pixelixe.md)\n- [Bannerbear API + MCP vs Clayzo](https://www.anchorterminal.com/compare/bannerbear-vs-clayzo.md)\n- [Bannerbear API + MCP vs Pixelixe](https://www.anchorterminal.com/compare/bannerbear-vs-pixelixe.md)\n- [Canva REST APIs + MCP vs Clayzo](https://www.anchorterminal.com/compare/canva-vs-clayzo.md)\n- [Canva REST APIs + MCP vs Pixelixe](https://www.anchorterminal.com/compare/canva-vs-pixelixe.md)\n- [Clayzo vs Photoroom API](https://www.anchorterminal.com/compare/clayzo-vs-photoroom.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 Clayzo](https://www.anchorterminal.com/compare/abyssale-vs-clayzo.md)\n- [Abyssale vs Pixelixe](https://www.anchorterminal.com/compare/abyssale-vs-pixelixe.md)\n- [Adobe Photoshop API vs Clayzo](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-clayzo.md)\n- [Clayzo vs Contentdrips API and MCP](https://www.anchorterminal.com/compare/clayzo-vs-contentdrips.md)\n- [Clayzo vs Creatomate](https://www.anchorterminal.com/compare/clayzo-vs-creatomate.md)\n- [Clayzo vs DynaPictures](https://www.anchorterminal.com/compare/clayzo-vs-dynapictures.md)\n- [Clayzo vs Layerre](https://www.anchorterminal.com/compare/clayzo-vs-layerre.md)\n- [Clayzo vs Osmo CLI](https://www.anchorterminal.com/compare/clayzo-vs-osmo-cli.md)\n- [Clayzo vs Pictify](https://www.anchorterminal.com/compare/clayzo-vs-pictify.md)\n- [Clayzo vs Placid API + MCP](https://www.anchorterminal.com/compare/clayzo-vs-placid.md)\n- [Clayzo vs PostNitro](https://www.anchorterminal.com/compare/clayzo-vs-postnitro.md)\n- [Clayzo vs Robolly](https://www.anchorterminal.com/compare/clayzo-vs-robolly.md)\n- [Clayzo vs Shotstack](https://www.anchorterminal.com/compare/clayzo-vs-shotstack.md)\n- [Clayzo vs Templated API + MCP](https://www.anchorterminal.com/compare/clayzo-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- [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-18",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "1.0",
    "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": "Clayzo vs Pixelixe",
        "url": ""
      }
    ],
    "description": "Clayzo scores 50.9 (D) to Pixelixe's 39.2 (E) for design rendering. Prices, MCP, x402, uptime and agent notes side by side.",
    "facts": [
      "Clayzo D 50.9",
      "Pixelixe E 39.2",
      "scores"
    ],
    "h1": "Clayzo vs Pixelixe",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/compare/clayzo-vs-pixelixe",
    "published": "2026-10-01",
    "section": "tools",
    "title": "Clayzo vs Pixelixe for AI agents in 2026: scores and prices",
    "toc": null,
    "updated": "2026-11-18",
    "url": "https://www.anchorterminal.com/compare/clayzo-vs-pixelixe"
  },
  "tokens": {
    "markdown": 4400,
    "slim": 1030
  },
  "version": 1
}
