{ "data": { "a": { "slug": "buttercms", "name": "ButterCMS", "vendor": "ButterCMS LLC", "vendorUrl": "https://buttercms.com", "kind": "http-api", "category": "cms", "summary": "ButterCMS is a hosted headless CMS with pages, collections and a blog engine. Agents read content through a REST Read API and create, update, publish and delete it through a REST Write API sold as a paid add-on.", "url": "https://www.anchorterminal.com/tools/buttercms", "markdownUrl": "https://www.anchorterminal.com/tools/buttercms.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/buttercms.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/buttercms.json", "dns": "buttercms.grade.anchorterminal.com", "repo": "https://github.com/ButterCMS/buttercms-js", "license": "Proprietary service under ButterCMS's terms of service. The SDKs and starter projects on GitHub are MIT", "transports": [ "http" ], "remoteUrl": "https://api.buttercms.com/v2", "packages": [ { "registry": "npm", "name": "buttercms" }, { "registry": "pypi", "name": "buttercms-python" } ], "auth": "api-key", "authNotes": "Self-serve for reads, paid add-on for writes. A person signs up in a browser and copies the read token from Settings. The write token exists only after the Write API add-on is bought under Settings, Billing, or enabled by support, and one docs page says this needs verification. The read token goes in the `auth_token` query parameter or an `Authorization: Token` header. The write token is accepted in the header only. There is one token of each kind per account, with no scopes, and the docs say tokens are rotated by contacting support. No OAuth, app review or sales approval for the listed plans.", "pricing": "freemium", "pricingNotes": "The Free plan needs no card and includes 50,000 API calls a month, but not the Write API. Writing needs Advanced ($249 a month, $224 billed yearly) or Professional ($399, $359 billed yearly) plus the Write API add-on, whose price is not published, with 2,000 or 5,000 write calls a month. Enterprise includes it and is sold through sales. Every plan has a 14-day trial (https://buttercms.com/pricing/, checked 2026-10-09).", "priceSummary": "$79 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API docs, the OpenAPI files or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 6929, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://buttercms.com/docs/api/overview", "llmsTxt": "https://buttercms.com/docs/llms.txt", "openapi": "https://buttercms.com/docs/api/openapi/openapi.yaml", "capabilities": [ "cms.content", "cms.publish", "cms.assets", "cms.localisation" ], "tags": [ "official", "hosted", "closed-source", "api-key", "openapi", "llms-txt", "webhooks", "free-tier", "no-card", "status-page", "javascript", "python", "php", "ruby" ], "lastRelease": "2025-09-04", "graded": true, "anchor": { "graded": true, "score": 51.4, "grade": "D", "agentReady": false, "rank": 1021, "ranked": true, "rankOf": 1486, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 64, "maintenance": 17, "payments": 20, "reliability": 82, "schema": 78, "security": 31, "transparency": 52 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -2, "negativeNotes": [ "9 October 2026. The docs page on AI tools showed `butter.page.update(...)` as the way to write through the JavaScript SDK, while the published SDK 3.0.3 has list, retrieve and search methods only and the SDK overview says to call REST for writes. By 4 November 2026 the page calls the Write API directly and says the SDK's Page resource is read-only; the term stays within the 12 months, as agentos's corrected claims did (https://buttercms.com/docs/build-your-app/third-party-integrations/ai-tools-integration.md, https://github.com/ButterCMS/buttercms-js). 2 points." ], "verdict": "The Read and Write APIs have a public OpenAPI 3.1 file, Markdown docs and a status page with no incident since October 2025. The Write API is a paid add-on from the $249 plan, capped at 2,000 or 5,000 calls a month. Writes answer 202 with no identifier, and no SDK has had a release since September 2025.", "bestFor": "A team already on a paid ButterCMS plan that wants an agent to draft and publish pages, collection items and blog posts in small volumes.", "strengths": [ "Public OpenAPI 3.1 files for the Read and Write APIs (28 operations in the combined file), a docs llms.txt and a Markdown copy of every docs page", "status.buttercms.com lists three components and no incident since 20 October 2025", "Writes create drafts unless `status` is `published`, and the write token is separate from the read token and accepted only in a header", "Media fields take a URL and the service copies the file into the media library, so one request creates an entry with its image", "Free plan with no card and 50,000 API calls a month for reading, and dollar prices for four plans on the pricing page" ], "weaknesses": [ "The Write API is a paid add-on on Advanced ($249 a month) and Professional ($399), capped at 2,000 and 5,000 write calls a month. Its price is not published", "Create and update calls answer 202 with `{\"status\": \"pending\"}` and no identifier, and there are no idempotency keys", "One read token and one write token per account, with no scopes. The docs say rotation is done by contacting support", "Page types and collections cannot be created through the API, pages cannot be deleted through it, and it has no version or rollback operation", "The terms are an undated website Terms of Service, the privacy policy dates from 15 August 2022 and covers the website, and a DPA is on request for Enterprise only", "No API changelog or deprecation policy was found. No SDK has had a release since JavaScript 3.0.3 on 4 September 2025, and that SDK has no write methods" ], "agentNotes": [ "End every path with a slash. A missing slash returns a 301, and the vendor counts the redirect and the retry as two API calls", "Send the write token only as `Authorization: Token \u003ctoken\u003e`. The `auth_token` query parameter works for reads only", "On page creation send every field key of the page type, with empty strings for fields left blank", "A 202 means queued, not saved. Read the entry back with `preview=1` to confirm, and check a slug exists before retrying a create", "Call the REST API directly for writes. The JavaScript SDK 3.0.3 has list, retrieve and search methods only" ], "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": 51.4 } ], "editorialScores": { "ergonomics": 64, "maintenance": 17, "payments": 20, "reliability": 82, "schema": 78, "security": 31, "transparency": 26 }, "provenanceScore": 78, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install buttercms --save", "http": "curl -H \"Authorization: Token your_api_token\" \\\n \"https://api.buttercms.com/v2/posts/\"" }, "letme": { "capability": "https://letme.dev/cms.content", "tool": "https://letme.dev/buttercms" }, "area": "business", "unitPrices": [ { "item": "Basic", "unit": "month", "usd": 79, "note": "billed monthly, $71 billed yearly, 100,000 API calls, no Write API" }, { "item": "Advanced", "unit": "month", "usd": 249, "note": "billed monthly, $224 billed yearly, 500,000 API calls, Write API add-on priced separately (up to 2,000 write calls)" }, { "item": "Professional", "unit": "month", "usd": 399, "note": "billed monthly, $359 billed yearly, 1M API calls, Write API add-on priced separately (up to 5,000 write calls)" } ], "provenance": { "legalEntity": "ButterCMS LLC", "domain": "buttercms.com", "domainRegistered": "2015-03-24", "endpointOnVendorDomain": true, "terms": "https://buttercms.com/terms/", "privacy": "https://buttercms.com/privacy/", "statusPage": "https://status.buttercms.com", "changelog": "", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The privacy policy (last modified 15 August 2022) names ButterCMS LLC. The terms name only Butter and ButterCMS, carry no date, give a San Francisco postal address for DMCA notices and choose Michigan law.", "The terms are written as website Terms of Service and define the Website to include the services on it. The Write API's OpenAPI file names this page as its licence, so it is the only published contract for the API. No separate service agreement, API terms or SLA document was found.", "The privacy policy covers information collected on the website and says nothing about content stored in the CMS. The docs say a data processing agreement is available to Enterprise customers on request.", "A status page post about a DNS outage on 9 September 2024 says ButterCMS was acquired by Tiugo Technologies, and the site's careers link goes to Tiugo's recruiting page.", "The API answers at api.buttercms.com and the dashboard at app.buttercms.com.", "buttercms.com/.well-known/security.txt returns 404. The docs give security@buttercms.com for vulnerability reports.", "RDAP for buttercms.com gives a registration date of 2015-03-24 and Amazon Registrar, Inc. as registrar.", "No API changelog was found on the site or in the docs index. The JavaScript SDK repository has a CHANGELOG.md." ], "score": 78 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/buttercms.json", "live": { "slug": "buttercms", "probe": { "target": "https://api.buttercms.com/v2", "method": "get", "lastAt": "2026-11-07T18:20:15.818598204Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "too many redirects", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 239, "samples30d": 7205, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 0 }, { "date": "2026-10-10", "probes": 247, "ok": 0 }, { "date": "2026-10-11", "probes": 247, "ok": 0 }, { "date": "2026-10-12", "probes": 247, "ok": 0 }, { "date": "2026-10-13", "probes": 248, "ok": 0 }, { "date": "2026-10-14", "probes": 249, "ok": 0 }, { "date": "2026-10-15", "probes": 253, "ok": 0 }, { "date": "2026-10-16", "probes": 252, "ok": 0 }, { "date": "2026-10-17", "probes": 253, "ok": 0 }, { "date": "2026-10-18", "probes": 256, "ok": 0 }, { "date": "2026-10-19", "probes": 255, "ok": 0 }, { "date": "2026-10-20", "probes": 252, "ok": 0 }, { "date": "2026-10-21", "probes": 253, "ok": 0 }, { "date": "2026-10-22", "probes": 253, "ok": 0 }, { "date": "2026-10-23", "probes": 248, "ok": 0 }, { "date": "2026-10-24", "probes": 251, "ok": 0 }, { "date": "2026-10-25", "probes": 250, "ok": 0 }, { "date": "2026-10-26", "probes": 252, "ok": 0 }, { "date": "2026-10-27", "probes": 249, "ok": 0 }, { "date": "2026-10-28", "probes": 251, "ok": 0 }, { "date": "2026-10-29", "probes": 249, "ok": 0 }, { "date": "2026-10-30", "probes": 248, "ok": 0 }, { "date": "2026-10-31", "probes": 251, "ok": 0 }, { "date": "2026-11-01", "probes": 249, "ok": 0 }, { "date": "2026-11-02", "probes": 250, "ok": 0 }, { "date": "2026-11-03", "probes": 248, "ok": 0 }, { "date": "2026-11-04", "probes": 246, "ok": 0 }, { "date": "2026-11-05", "probes": 185, "ok": 0 }, { "date": "2026-11-06", "probes": 241, "ok": 0 }, { "date": "2026-11-07", "probes": 187, "ok": 0 } ], "outages": [ { "start": "2026-10-09T15:43:00.096294667Z", "end": "0001-01-01T00:00:00Z", "note": "too many redirects" } ] }, "vendorStatus": { "page": "https://status.buttercms.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:20:37.678717104Z" }, "versions": [ { "registry": "github", "name": "ButterCMS/buttercms-js", "version": "v3.0.3", "released": "2025-09-04", "seenAt": "2026-11-06T23:13:00.320392722Z" }, { "registry": "npm", "name": "buttercms", "version": "3.0.3", "seenAt": "2026-11-06T23:12:59.922427706Z" }, { "registry": "pypi", "name": "buttercms-python", "version": "2.1.1", "released": "2024-05-07", "seenAt": "2026-11-06T23:13:00.12522511Z" } ], "githubStars": 164, "npmWeekly": 9389, "pypiWeekly": 301, "securityTxt": { "url": "https://buttercms.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T15:59:49.204405911Z" }, "llmsTxt": { "url": "https://buttercms.com/docs/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:45.80373153Z" }, "domain": { "domain": "buttercms.com", "registered": "2015-03-24", "source": "https://rdap.verisign.com/com/v1/domain/buttercms.com", "checkedAt": "2026-11-01T14:13:03.897204984Z" }, "pages": [ { "url": "https://buttercms.com/pricing/", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:00:36.294009426Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9ba825b44b86" }, { "url": "https://buttercms.com/privacy/", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:00:38.426465317Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "908b6461f1b9" }, { "url": "https://buttercms.com/terms/", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:00:40.417468366Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8862b63c94a5" } ], "github": { "repo": "buttercms/buttercms-js", "checkedAt": "2026-11-02T08:37:25.410869031Z", "stars": 164, "archived": false, "issuesEnabled": true, "pushedAt": "2025-11-13T15:53:09Z", "openIssues": 2, "openPRs": 1, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 0, "ci": { "branch": "master", "runs": 2, "success": 1, "failure": 0, "other": 1, "latest": "skipped", "latestAt": "2025-11-13T15:53:02Z" }, "replies": { "sampled": 25, "unanswered": 2, "medianDays": 13 } }, "updatedAt": "2026-11-07T18:20:15.818598204Z" } }, "answer": "dotCMS scores 57.7 (C) on agent readiness against ButterCMS's 51.4 (D), and leads in 5 of 7 scored categories. ButterCMS leads on reliability and schema \u0026 documentation.", "b": { "slug": "dotcms", "name": "dotCMS", "vendor": "dotCMS LLC", "vendorUrl": "https://www.dotcms.com", "kind": "mcp", "category": "cms", "summary": "dotCMS is an enterprise CMS with headless REST APIs, workflows and push publishing, run as dotCMS Cloud or self-hosted. Agents use the @dotcms/mcp-server package, which searches the instance's OpenAPI spec and runs API calls in a sandbox.", "url": "https://www.anchorterminal.com/tools/dotcms", "markdownUrl": "https://www.anchorterminal.com/tools/dotcms.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/dotcms.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/dotcms.json", "dns": "dotcms.grade.anchorterminal.com", "repo": "https://github.com/dotCMS/core", "license": "BUSL-1.1", "transports": [ "stdio" ], "packages": [ { "registry": "npm", "name": "@dotcms/mcp-server" } ], "auth": "api-key", "authNotes": "The MCP server reads DOTCMS_URL and AUTH_TOKEN. API tokens are JWTs issued for a dotCMS user, carry that user's role permissions, take an expiry in days, and are created by administrators in the user manager or through /api/v1/authentication/api-token. The docs recommend a separate user and role per application; the MCP server needs write permission for content types, content and workflows. Tokens are injected outside the sandbox, so sandboxed code never sees them.", "pricing": "freemium", "pricingNotes": "dotCMS is free with every capability for companies under $5 million in revenue under its BSL licence, self-hosted. Cloud plans (Starter, Professional, Business, Enterprise) are priced on request, with monthly request and bandwidth allowances and SLAs of 99.5 to 99.9 per cent.", "priceSummary": "Freemium", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the MCP README, the dev docs or the pricing page (checked 2026-11-06).", "endpoints": [] }, "toolCount": 7, "popularity": { "githubStars": null, "npmWeekly": 43, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://dev.dotcms.com/docs/build/integrations/dotai/mcp-server", "llmsTxt": "https://dev.dotcms.com/llms.txt", "capabilities": [ "cms.content", "cms.publish", "cms.assets", "cms.schema", "cms.localisation" ], "tags": [ "official", "mcp", "stdio", "self-hosted", "hosted", "source-available", "llms-txt", "sales-led", "sla", "typescript" ], "lastRelease": "2026-09-02", "graded": true, "anchor": { "graded": true, "score": 57.7, "grade": "C", "agentReady": false, "rank": 780, "ranked": true, "rankOf": 1486, "categoryRank": 12, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 75, "payments": 35, "reliability": 47, "schema": 65, "security": 63, "transparency": 54 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-06" }, "negative": 0, "verdict": "dotCMS's MCP server keeps the tool list to seven by letting the agent search the instance's OpenAPI spec and run API calls in a sandbox that never sees the token. It is a pre-1.0 package that needs a write token, and cloud prices are on request.", "bestFor": "Enterprises already on dotCMS who want an agent to manage content and pages.", "strengths": [ "Seven tools in code mode, with the instance's OpenAPI spec searchable from the sandbox", "The API token stays outside the sandbox, which only receives results", "JWT tokens per user with role permissions and an expiry", "security.txt with PGP, a bounty-backed disclosure policy and LTS security backports", "Free with every capability for organisations under $5 million in revenue" ], "weaknesses": [ "Pre-1.0 package, with the dev docs still pointing at the beta tag", "The server needs a token with write permission for content types, content and workflows", "execute can call any endpoint, and no read-only mode or annotations were found", "Cloud prices are on request only", "Source-available under the BSL, not an OSI licence" ], "agentNotes": [ "Search the spec with `search` before writing an `execute` call, and return only the fields you need", "Use a token for a dedicated user and role, not an administrator's", "Confirm with the user before execute calls that publish, archive or delete content", "Keep results small with pick and first, since output is capped at about 25,000 characters", "Use download_assets for theme folders so files land on disk instead of in context" ], "metrics": { "kind": "local", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 57.7 } ], "editorialScores": { "ergonomics": 68, "maintenance": 75, "payments": 35, "reliability": 47, "schema": 65, "security": 63, "transparency": 51 }, "provenanceScore": 57, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npx -y @dotcms/mcp-server", "config": { "mcpServers": { "dotcms": { "args": [ "-y", "@dotcms/mcp-server" ], "command": "npx", "env": { "AUTH_TOKEN": "your-api-token", "DOTCMS_URL": "https://your-dotcms-instance.com" } } } } }, "letme": { "capability": "https://letme.dev/cms.content", "tool": "https://letme.dev/dotcms" }, "area": "business", "provenance": { "legalEntity": "dotCMS LLC", "domain": "dotcms.com", "domainRegistered": "", "endpointOnVendorDomain": false, "terms": "https://github.com/dotCMS/core/blob/main/LICENSE", "privacy": "https://dev.dotcms.com/docs/manage/access-and-security/security-and-privacy/privacy-policy", "statusPage": "", "changelog": "https://dev.dotcms.com/docs/reference/releases/product-versions/changelogs", "securityTxt": "valid", "checked": "2026-11-06", "notes": [ "The MCP server runs locally and calls the customer's own dotCMS instance, so the endpoint isn't on a dotCMS domain.", "The privacy policy, last updated 8 September 2026, covers dotCMS's websites only and names dotCMS Holdings, LLC, dotCMS Services LLC and dotCMS LLC.", "www.dotcms.com/robots.txt disallows /docs/ and /utils/; dev.dotcms.com allows all with Content-Signal ai-train=yes, search=yes, ai-input=yes.", "www.dotcms.com/terms-of-service and /privacy-policy returned 404; no cloud terms of service were found, so the licence stands in for terms.", "No status page answered (status.dotcms.com refused the connection)." ], "score": 57 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/dotcms.json", "live": { "slug": "dotcms", "versions": [ { "registry": "github", "name": "dotCMS/core", "version": "dotcms-cli-26.11.06-03", "released": "2026-11-06", "seenAt": "2026-11-06T23:22:22.409374032Z" }, { "registry": "npm", "name": "@dotcms/mcp-server", "version": "0.1.1", "seenAt": "2026-11-06T23:22:21.577680774Z" } ], "githubStars": 971, "npmWeekly": 43, "securityTxt": { "url": "https://dotcms.com/.well-known/security.txt", "state": "valid", "expires": "2027-06-09T23:59:59.000Z", "checkedAt": "2026-11-07T16:00:46.289271049Z" }, "llmsTxt": { "url": "https://dev.dotcms.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:19.058875451Z" }, "pages": [ { "url": "https://dev.dotcms.com/docs/reference/releases/product-versions/changelogs", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:02:43.439634709Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "14706a7e3d20" }, { "url": "https://dev.dotcms.com/docs/manage/access-and-security/security-and-privacy/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:02:39.904485204Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b8fe703d4258" }, { "url": "https://raw.githubusercontent.com/dotCMS/core/main/LICENSE", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:20:41.976083247Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "1dd3baa6b46f" } ], "updatedAt": "2026-11-07T16:00:46.289271049Z" } }, "edges": [ { "by": 58, "category": "maintenance", "leads": "dotcms", "name": "Maintenance \u0026 community", "reasons": { "a": "No dated API changelog was found, and no dated API change in the docs. The docs sitemap's page dates record no change, so they don't set recency. The newest SDK release across the ten official SDKs is `buttercms` 3.0.3 on 4 September 2025 (Python 2.1.1 on 7 May 2024, .NET 2.1.1 on 16 April 2025, the others older), more than 180 days ago (0 of 30). No three releases or dated changelog entries in 90 days (0). Support by chat and email, a knowledge base and public SDK repositories, with no public changelog (5 of 15). Ten official SDKs are listed and none has a release in the last year (7 of 15, a partial kept). The JavaScript SDK has test and release workflows and moved to trusted publishing in November 2025, with no commits in the last 90 days (5 of 10).", "b": "dotCMS core tagged v26.11.06-03 on 6 November 2026; the MCP package's last release was 0.1.1 on 2 September (30). Core tags several times a week (20). GitHub issues and a community forum; response times weren't read because the GitHub API refused us for its rate limit (10 of 25). Not in the official MCP registry; official JavaScript client libraries (8 of 15). The MCP package's dependencies and CI state weren't read (7 of 10). 30+20+10+8+7 = 75." }, "scores": { "a": 17, "b": 75 } }, { "by": 35, "category": "reliability", "leads": "buttercms", "name": "Reliability", "reasons": { "a": "Graded on the hosted Read and Write APIs. Public status page on Atlassian Statuspage with CDN, API and Login Page components and a history feed (20). The feed's newest incidents are two on 20 October 2025, so the 90 days to 4 November 2026 are clean (30). Limits are published as monthly quotas by plan, from 50,000 calls on Free to 1M on Professional, with 2,000 or 5,000 write calls on the add-on. No per-second limit is published (10 of 15, a partial kept from the 9 October check). Free and trial accounts get a 429 that the docs say may carry `Retry-After`, the docs show exponential backoff for 5xx errors, and the bulk-operations page says to check whether content exists before creating it to avoid duplicates during retries. There are no idempotency keys, so safe-retry guidance without keys (12). The pricing page lists an SLA on Enterprise with no SLA document or figure, which this run reads as 0. The v2 API is generally available (10).", "b": "Read with the local-software lines, since the MCP server is a stdio package the owner runs against their own instance. Official npm package with Node 20 or later and Bun stated (20). The monorepo has CI and the MCP app has vitest tests and smoke tests; whether they pass on main wasn't read (12 of 25). Open issues weren't read because the GitHub API refused us for its rate limit (10 of 25). 0.1.0 and 0.1.1 without release notes for the package (5 of 15). Pre-1.0, and the dev docs still call it beta (0). 20+12+10+5+0 = 47." }, "scores": { "a": 82, "b": 47 } }, { "by": 32, "category": "security", "leads": "dotcms", "name": "Security \u0026 auth", "reasons": { "a": "One read token and one write token per account, with no scopes, and the docs say rotation is done by contacting support (20 for plain revocable keys, less the fixed 10 because the read token is documented as an `auth_token` query parameter, 10 of 30). That token also returns drafts with `preview=1`. The read token is a read-only credential and writes default to draft. No approval step for API writes was found, and approval workflows are listed on Enterprise (10 of 20). The API returns stored content, and no guidance on treating it as untrusted input was found (3 of 15). Audit logs and access logs are listed as Enterprise functions, and versions record who saved them (6 of 15). A responsible-disclosure section in the docs gives security@buttercms.com and says reports get a prompt response, with no stated time, and the security page describes penetration tests. No security.txt, no bug bounty, and the certifications listed are those of the AWS and Heroku data centres (7 of 20).", "b": "JWT API tokens per user with role permissions and an expiry, created only by administrators (25 of 30). A read-only token can be made through a restricted role, but the MCP server asks for write permission; workflows support multiple-approval steps (14 of 20). Content returned from the CMS reaches the agent, and the sandbox isolates the token, with no prompt-injection guidance (5 of 15). Audit logging for API calls wasn't established in the pages read (5 of 15). A valid security.txt with PGP, a responsible disclosure policy with bounties, LTS security backports and a public list of known security issues, which is drawn by script and couldn't be read. No certification was found (14 of 20). 25+14+5+5+14 = 63." }, "scores": { "a": 31, "b": 63 } }, { "by": 15, "category": "payments", "leads": "dotcms", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Four plans have public dollar prices, the Write API add-on's price is not published and Enterprise is through sales (10). The Free plan needs no card and covers the Read API. Writing needs a paid plan and the add-on, and we did not establish whether the 14-day trial includes it (10 of 20). A person signs up in a browser, and the write token needs a purchase or a request to support (0).", "b": "Scored with the self-hosted rule, with prices from the cloud plans. No x402, MPP or L402 (0). Cloud prices are on request only (0). Free with every capability under $5 million in revenue under the BSL, with no card (20). Self-hosting needs no dotCMS account, and tokens can be minted by API on one's own instance (15 of 20). 0+0+20+15 = 35." }, "scores": { "a": 20, "b": 35 } }, { "by": 13, "category": "schema", "leads": "buttercms", "name": "Schema \u0026 documentation", "reasons": { "a": "Public OpenAPI 3.1 files for the whole API, the Read API, the Write API and webhooks, linked from the docs index. The combined file has 28 operations on 4 November 2026, 18 reads and 10 writes (25). A docs llms.txt and a Markdown copy of every docs page (10). All operations have a description, and the write descriptions state field rules, defaults and what the API cannot do. The docs say when to use an SDK and when to call REST (16 of 20). Request bodies have required fields and 40 enums in the combined file, but the `fields` object depends on each account's page types and no endpoint returns those types (9 of 15). 328 examples in the combined file and a page of status codes with causes and sample bodies (13 of 15). The version is in the `/v2` path. No API changelog was found (5 of 15).", "b": "The search tool exposes the instance's own OpenAPI spec, so the contract is machine-readable, though the tools themselves take JavaScript code (20 of 25). llms.txt and Markdown pages on dev.dotcms.com (10). The README says what each tool is for and gives examples; when not to use them isn't stated (12 of 20). Code strings rather than typed parameters for search and execute (4 of 15). Examples for both tools; error behaviour of the sandbox isn't documented (9 of 15). dotCMS changelogs are dated; the MCP package has no changelog (10 of 15). 20+10+12+4+9+10 = 65." }, "scores": { "a": 78, "b": 65 } } ], "facts": [ { "a": "HTTP API", "b": "MCP server", "name": "Kind" }, { "a": "ButterCMS LLC", "b": "dotCMS LLC", "name": "Vendor" }, { "a": "https://api.buttercms.com/v2", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "stdio", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under ButterCMS's terms of service. The SDKs and starter projects on GitHub are MIT", "b": "BUSL-1.1", "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": "2025-09-04", "b": "2026-09-02", "name": "Last release" }, { "a": "no date given", "b": "no date given", "name": "Terms last updated" }, { "a": "2022-08-15", "b": "2026-09-08", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "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": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "6.9k npm/wk", "b": "43 npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "dotCMS scores 57.7 (C) on agent readiness against ButterCMS's 51.4 (D), and leads in 5 of 7 scored categories. ButterCMS leads on reliability and schema \u0026 documentation.", "question": "Which is better for AI agents, ButterCMS or dotCMS?" }, { "answer": "Both need an API key.", "question": "Do ButterCMS and dotCMS need an API key?" }, { "answer": "ButterCMS has a hosted endpoint at https://api.buttercms.com/v2. dotCMS runs on your own machine, with no hosted endpoint listed.", "question": "Can an agent call ButterCMS and dotCMS without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 82 against 47", "Schema \u0026 documentation, 78 against 65" ], "also": [ "A hosted endpoint, with nothing to install", "Free to start without a card" ], "goodFor": "A team already on a paid ButterCMS plan that wants an agent to draft and publish pages, collection items and blog posts in small volumes.", "slug": "buttercms", "watchFor": "The Write API is a paid add-on on Advanced ($249 a month) and Professional ($399), capped at 2,000 and 5,000 write calls a month. Its price is not published" }, { "aheadOn": [ "Security \u0026 auth, 63 against 31", "Payments \u0026 pricing, 35 against 20", "Maintenance \u0026 community, 75 against 17" ], "also": [ "Runs on your own machine" ], "goodFor": "Enterprises already on dotCMS who want an agent to manage content and pages.", "slug": "dotcms", "watchFor": "Pre-1.0 package, with the dev docs still pointing at the beta tag" } ], "history": { "buttercms": [ { "causes": [ "method" ], "date": "2026-11-04", "delta": -2, "from": 53.4, "fromGrade": "D", "to": 51.4, "toGrade": "D" }, { "causes": [ "evidence" ], "date": "2026-10-28", "delta": 0.1, "from": 53.3, "fromGrade": "D", "to": 53.4, "toGrade": "D" } ], "dotcms": null }, "job": { "capability": "cms.content", "name": "Content management" }, "others": [ { "json": "https://www.anchorterminal.com/compare/bcms-vs-buttercms.json", "title": "BCMS vs ButterCMS", "url": "https://www.anchorterminal.com/compare/bcms-vs-buttercms" }, { "json": "https://www.anchorterminal.com/compare/bcms-vs-dotcms.json", "title": "BCMS vs dotCMS", "url": "https://www.anchorterminal.com/compare/bcms-vs-dotcms" }, { "json": "https://www.anchorterminal.com/compare/buttercms-vs-contentstack.json", "title": "ButterCMS vs Contentstack", "url": "https://www.anchorterminal.com/compare/buttercms-vs-contentstack" }, { "json": "https://www.anchorterminal.com/compare/buttercms-vs-cosmic.json", "title": "ButterCMS vs Cosmic", "url": "https://www.anchorterminal.com/compare/buttercms-vs-cosmic" }, { "json": "https://www.anchorterminal.com/compare/buttercms-vs-datocms.json", "title": "ButterCMS vs DatoCMS", "url": "https://www.anchorterminal.com/compare/buttercms-vs-datocms" }, { "json": "https://www.anchorterminal.com/compare/buttercms-vs-directus.json", "title": "ButterCMS vs Directus", "url": "https://www.anchorterminal.com/compare/buttercms-vs-directus" }, { "json": "https://www.anchorterminal.com/compare/buttercms-vs-ghost.json", "title": "ButterCMS vs Ghost", "url": "https://www.anchorterminal.com/compare/buttercms-vs-ghost" }, { "json": "https://www.anchorterminal.com/compare/buttercms-vs-hygraph.json", "title": "ButterCMS vs Hygraph", "url": "https://www.anchorterminal.com/compare/buttercms-vs-hygraph" }, { "json": "https://www.anchorterminal.com/compare/buttercms-vs-kontent-ai.json", "title": "ButterCMS vs Kontent.ai", "url": "https://www.anchorterminal.com/compare/buttercms-vs-kontent-ai" }, { "json": "https://www.anchorterminal.com/compare/buttercms-vs-payload.json", "title": "ButterCMS vs Payload", "url": "https://www.anchorterminal.com/compare/buttercms-vs-payload" }, { "json": "https://www.anchorterminal.com/compare/buttercms-vs-prismic.json", "title": "ButterCMS vs Prismic", "url": "https://www.anchorterminal.com/compare/buttercms-vs-prismic" }, { "json": "https://www.anchorterminal.com/compare/buttercms-vs-sanity.json", "title": "ButterCMS vs Sanity", "url": "https://www.anchorterminal.com/compare/buttercms-vs-sanity" }, { "json": "https://www.anchorterminal.com/compare/buttercms-vs-storyblok.json", "title": "ButterCMS vs Storyblok", "url": "https://www.anchorterminal.com/compare/buttercms-vs-storyblok" }, { "json": "https://www.anchorterminal.com/compare/buttercms-vs-strapi.json", "title": "ButterCMS vs Strapi", "url": "https://www.anchorterminal.com/compare/buttercms-vs-strapi" }, { "json": "https://www.anchorterminal.com/compare/buttercms-vs-webflow.json", "title": "ButterCMS vs Webflow", "url": "https://www.anchorterminal.com/compare/buttercms-vs-webflow" }, { "json": "https://www.anchorterminal.com/compare/buttercms-vs-wordpress.json", "title": "ButterCMS vs WordPress", "url": "https://www.anchorterminal.com/compare/buttercms-vs-wordpress" }, { "json": "https://www.anchorterminal.com/compare/contentstack-vs-dotcms.json", "title": "Contentstack vs dotCMS", "url": "https://www.anchorterminal.com/compare/contentstack-vs-dotcms" }, { "json": "https://www.anchorterminal.com/compare/cosmic-vs-dotcms.json", "title": "Cosmic vs dotCMS", "url": "https://www.anchorterminal.com/compare/cosmic-vs-dotcms" }, { "json": "https://www.anchorterminal.com/compare/datocms-vs-dotcms.json", "title": "DatoCMS vs dotCMS", "url": "https://www.anchorterminal.com/compare/datocms-vs-dotcms" }, { "json": "https://www.anchorterminal.com/compare/directus-vs-dotcms.json", "title": "Directus vs dotCMS", "url": "https://www.anchorterminal.com/compare/directus-vs-dotcms" }, { "json": "https://www.anchorterminal.com/compare/dotcms-vs-ghost.json", "title": "dotCMS vs Ghost", "url": "https://www.anchorterminal.com/compare/dotcms-vs-ghost" }, { "json": "https://www.anchorterminal.com/compare/dotcms-vs-hygraph.json", "title": "dotCMS vs Hygraph", "url": "https://www.anchorterminal.com/compare/dotcms-vs-hygraph" }, { "json": "https://www.anchorterminal.com/compare/dotcms-vs-kontent-ai.json", "title": "dotCMS vs Kontent.ai", "url": "https://www.anchorterminal.com/compare/dotcms-vs-kontent-ai" }, { "json": "https://www.anchorterminal.com/compare/dotcms-vs-payload.json", "title": "dotCMS vs Payload", "url": "https://www.anchorterminal.com/compare/dotcms-vs-payload" }, { "json": "https://www.anchorterminal.com/compare/dotcms-vs-prismic.json", "title": "dotCMS vs Prismic", "url": "https://www.anchorterminal.com/compare/dotcms-vs-prismic" }, { "json": "https://www.anchorterminal.com/compare/dotcms-vs-sanity.json", "title": "dotCMS vs Sanity", "url": "https://www.anchorterminal.com/compare/dotcms-vs-sanity" }, { "json": "https://www.anchorterminal.com/compare/dotcms-vs-storyblok.json", "title": "dotCMS vs Storyblok", "url": "https://www.anchorterminal.com/compare/dotcms-vs-storyblok" }, { "json": "https://www.anchorterminal.com/compare/dotcms-vs-strapi.json", "title": "dotCMS vs Strapi", "url": "https://www.anchorterminal.com/compare/dotcms-vs-strapi" }, { "json": "https://www.anchorterminal.com/compare/dotcms-vs-webflow.json", "title": "dotCMS vs Webflow", "url": "https://www.anchorterminal.com/compare/dotcms-vs-webflow" }, { "json": "https://www.anchorterminal.com/compare/dotcms-vs-wordpress.json", "title": "dotCMS vs WordPress", "url": "https://www.anchorterminal.com/compare/dotcms-vs-wordpress" } ], "panel": null, "scores": [ { "buttercms": 82, "by": 35, "dotcms": 47, "edge": "buttercms", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "buttercms": 78, "by": 13, "dotcms": 65, "edge": "buttercms", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "buttercms": 64, "by": 4, "dotcms": 68, "edge": "dotcms", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "buttercms": 31, "by": 32, "dotcms": 63, "edge": "dotcms", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "buttercms": 20, "by": 15, "dotcms": 35, "edge": "dotcms", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "buttercms": 17, "by": 58, "dotcms": 75, "edge": "dotcms", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "buttercms": 52, "by": 2, "dotcms": 54, "edge": "dotcms", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "dotCMS scores 57.7 (C) on agent readiness against ButterCMS's 51.4 (D), and leads in 5 of 7 scored categories. ButterCMS leads on reliability and schema \u0026 documentation. Both do content management.", "tasks": null, "tutorials": [], "verdicts": { "buttercms": "The Read and Write APIs have a public OpenAPI 3.1 file, Markdown docs and a status page with no incident since October 2025. The Write API is a paid add-on from the $249 plan, capped at 2,000 or 5,000 calls a month. Writes answer 202 with no identifier, and no SDK has had a release since September 2025.", "dotcms": "dotCMS's MCP server keeps the tool list to seven by letting the agent search the instance's OpenAPI spec and run API calls in a sandbox that never sees the token. It is a pre-1.0 package that needs a write token, and cloud prices are on request." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/buttercms-vs-dotcms", "json": "https://www.anchorterminal.com/compare/buttercms-vs-dotcms.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/buttercms-vs-dotcms.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/buttercms-vs-dotcms.min.md" }, "markdown": "dotCMS scores 57.7 (C) on agent readiness against ButterCMS's 51.4 (D), and leads in 5 of 7 scored categories. ButterCMS leads on reliability and schema \u0026 documentation. Both do content management.\n\n- ButterCMS: grade D, 51.4/100, rank #1021 of 1486. Markdown https://www.anchorterminal.com/tools/buttercms.md · JSON https://www.anchorterminal.com/api/v1/tools/buttercms.json\n- dotCMS: grade C, 57.7/100, rank #780 of 1486. Markdown https://www.anchorterminal.com/tools/dotcms.md · JSON https://www.anchorterminal.com/api/v1/tools/dotcms.json\n- Best headless CMS and website publishing for AI agents: https://www.anchorterminal.com/best/cms/index.md\n- All 136 cms comparisons: https://www.anchorterminal.com/compare/cms/index.md\n\n## Which one, for what\n\n### ButterCMS (D)\n\nGood for: A team already on a paid ButterCMS plan that wants an agent to draft and publish pages, collection items and blog posts in small volumes.\n\nAhead on:\n- Reliability, 82 against 47\n- Schema \u0026 documentation, 78 against 65\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n- Free to start without a card\n\nWatch for: The Write API is a paid add-on on Advanced ($249 a month) and Professional ($399), capped at 2,000 and 5,000 write calls a month. Its price is not published\n\n### dotCMS (C)\n\nGood for: Enterprises already on dotCMS who want an agent to manage content and pages.\n\nAhead on:\n- Security \u0026 auth, 63 against 31\n- Payments \u0026 pricing, 35 against 20\n- Maintenance \u0026 community, 75 against 17\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: Pre-1.0 package, with the dev docs still pointing at the beta tag\n\n\n## Why the edge\n\n### Maintenance \u0026 community: dotCMS +58\n\n- ButterCMS (17): No dated API changelog was found, and no dated API change in the docs. The docs sitemap's page dates record no change, so they don't set recency. The newest SDK release across the ten official SDKs is `buttercms` 3.0.3 on 4 September 2025 (Python 2.1.1 on 7 May 2024, .NET 2.1.1 on 16 April 2025, the others older), more than 180 days ago (0 of 30). No three releases or dated changelog entries in 90 days (0). Support by chat and email, a knowledge base and public SDK repositories, with no public changelog (5 of 15). Ten official SDKs are listed and none has a release in the last year (7 of 15, a partial kept). The JavaScript SDK has test and release workflows and moved to trusted publishing in November 2025, with no commits in the last 90 days (5 of 10).\n- dotCMS (75): dotCMS core tagged v26.11.06-03 on 6 November 2026; the MCP package's last release was 0.1.1 on 2 September (30). Core tags several times a week (20). GitHub issues and a community forum; response times weren't read because the GitHub API refused us for its rate limit (10 of 25). Not in the official MCP registry; official JavaScript client libraries (8 of 15). The MCP package's dependencies and CI state weren't read (7 of 10). 30+20+10+8+7 = 75.\n\n### Reliability: ButterCMS +35\n\n- ButterCMS (82): Graded on the hosted Read and Write APIs. Public status page on Atlassian Statuspage with CDN, API and Login Page components and a history feed (20). The feed's newest incidents are two on 20 October 2025, so the 90 days to 4 November 2026 are clean (30). Limits are published as monthly quotas by plan, from 50,000 calls on Free to 1M on Professional, with 2,000 or 5,000 write calls on the add-on. No per-second limit is published (10 of 15, a partial kept from the 9 October check). Free and trial accounts get a 429 that the docs say may carry `Retry-After`, the docs show exponential backoff for 5xx errors, and the bulk-operations page says to check whether content exists before creating it to avoid duplicates during retries. There are no idempotency keys, so safe-retry guidance without keys (12). The pricing page lists an SLA on Enterprise with no SLA document or figure, which this run reads as 0. The v2 API is generally available (10).\n- dotCMS (47): Read with the local-software lines, since the MCP server is a stdio package the owner runs against their own instance. Official npm package with Node 20 or later and Bun stated (20). The monorepo has CI and the MCP app has vitest tests and smoke tests; whether they pass on main wasn't read (12 of 25). Open issues weren't read because the GitHub API refused us for its rate limit (10 of 25). 0.1.0 and 0.1.1 without release notes for the package (5 of 15). Pre-1.0, and the dev docs still call it beta (0). 20+12+10+5+0 = 47.\n\n### Security \u0026 auth: dotCMS +32\n\n- ButterCMS (31): One read token and one write token per account, with no scopes, and the docs say rotation is done by contacting support (20 for plain revocable keys, less the fixed 10 because the read token is documented as an `auth_token` query parameter, 10 of 30). That token also returns drafts with `preview=1`. The read token is a read-only credential and writes default to draft. No approval step for API writes was found, and approval workflows are listed on Enterprise (10 of 20). The API returns stored content, and no guidance on treating it as untrusted input was found (3 of 15). Audit logs and access logs are listed as Enterprise functions, and versions record who saved them (6 of 15). A responsible-disclosure section in the docs gives security@buttercms.com and says reports get a prompt response, with no stated time, and the security page describes penetration tests. No security.txt, no bug bounty, and the certifications listed are those of the AWS and Heroku data centres (7 of 20).\n- dotCMS (63): JWT API tokens per user with role permissions and an expiry, created only by administrators (25 of 30). A read-only token can be made through a restricted role, but the MCP server asks for write permission; workflows support multiple-approval steps (14 of 20). Content returned from the CMS reaches the agent, and the sandbox isolates the token, with no prompt-injection guidance (5 of 15). Audit logging for API calls wasn't established in the pages read (5 of 15). A valid security.txt with PGP, a responsible disclosure policy with bounties, LTS security backports and a public list of known security issues, which is drawn by script and couldn't be read. No certification was found (14 of 20). 25+14+5+5+14 = 63.\n\n### Payments \u0026 pricing: dotCMS +15\n\n- ButterCMS (20): No x402, MPP or L402 (0). Four plans have public dollar prices, the Write API add-on's price is not published and Enterprise is through sales (10). The Free plan needs no card and covers the Read API. Writing needs a paid plan and the add-on, and we did not establish whether the 14-day trial includes it (10 of 20). A person signs up in a browser, and the write token needs a purchase or a request to support (0).\n- dotCMS (35): Scored with the self-hosted rule, with prices from the cloud plans. No x402, MPP or L402 (0). Cloud prices are on request only (0). Free with every capability under $5 million in revenue under the BSL, with no card (20). Self-hosting needs no dotCMS account, and tokens can be minted by API on one's own instance (15 of 20). 0+0+20+15 = 35.\n\n### Schema \u0026 documentation: ButterCMS +13\n\n- ButterCMS (78): Public OpenAPI 3.1 files for the whole API, the Read API, the Write API and webhooks, linked from the docs index. The combined file has 28 operations on 4 November 2026, 18 reads and 10 writes (25). A docs llms.txt and a Markdown copy of every docs page (10). All operations have a description, and the write descriptions state field rules, defaults and what the API cannot do. The docs say when to use an SDK and when to call REST (16 of 20). Request bodies have required fields and 40 enums in the combined file, but the `fields` object depends on each account's page types and no endpoint returns those types (9 of 15). 328 examples in the combined file and a page of status codes with causes and sample bodies (13 of 15). The version is in the `/v2` path. No API changelog was found (5 of 15).\n- dotCMS (65): The search tool exposes the instance's own OpenAPI spec, so the contract is machine-readable, though the tools themselves take JavaScript code (20 of 25). llms.txt and Markdown pages on dev.dotcms.com (10). The README says what each tool is for and gives examples; when not to use them isn't stated (12 of 20). Code strings rather than typed parameters for search and execute (4 of 15). Examples for both tools; error behaviour of the sandbox isn't documented (9 of 15). dotCMS changelogs are dated; the MCP package has no changelog (10 of 15). 20+10+12+4+9+10 = 65.\n\n## Score by category\n\n| Category | Weight | ButterCMS | dotCMS | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 82 | 47 | ButterCMS +35 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 78 | 65 | ButterCMS +13 |\n| Agent ergonomics | 13% (16.2 this run) | 64 | 68 | dotCMS +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 31 | 63 | dotCMS +32 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 35 | dotCMS +15 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 17 | 75 | dotCMS +58 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 52 | 54 | dotCMS +2 |\n| Negative events | ≤15 | -2 | 0 | |\n| **Total** | | **51.4 · D** | **57.7 · C** | |\n\n## Facts side by side\n\n| Fact | ButterCMS | dotCMS |\n| --- | --- | --- |\n| Kind | HTTP API | MCP server |\n| Vendor | ButterCMS LLC | dotCMS LLC |\n| Hosted endpoint | `https://api.buttercms.com/v2` | no (local only) |\n| Transports | HTTP | stdio |\n| Auth | API key | API key |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Licence | Proprietary service under ButterCMS's terms of service. The SDKs and starter projects on GitHub are MIT | BUSL-1.1 |\n| Tools exposed | none | 7 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | 2025-09-04 | 2026-09-02 |\n| Terms last updated | no date given | no date given |\n| Privacy policy last updated | 2022-08-15 | 2026-09-08 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | 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 | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 6.9k npm/wk | 43 npm/wk |\n\n## How the scores have moved\n\n### ButterCMS\n\n- -2.0 on 4 November 2026: checklist\n- +0.1 on 28 October 2026: new evidence\n\n### dotCMS\n\nNo score change since it was listed.\n\n## Verdicts\n\n**ButterCMS.** The Read and Write APIs have a public OpenAPI 3.1 file, Markdown docs and a status page with no incident since October 2025. The Write API is a paid add-on from the $249 plan, capped at 2,000 or 5,000 calls a month. Writes answer 202 with no identifier, and no SDK has had a release since September 2025.\n\n**dotCMS.** dotCMS's MCP server keeps the tool list to seven by letting the agent search the instance's OpenAPI spec and run API calls in a sandbox that never sees the token. It is a pre-1.0 package that needs a write token, and cloud prices are on request.\n\n## Before you call either\n\n### ButterCMS\n\n1. End every path with a slash. A missing slash returns a 301, and the vendor counts the redirect and the retry as two API calls\n2. Send the write token only as `Authorization: Token \u003ctoken\u003e`. The `auth_token` query parameter works for reads only\n3. On page creation send every field key of the page type, with empty strings for fields left blank\n4. A 202 means queued, not saved. Read the entry back with `preview=1` to confirm, and check a slug exists before retrying a create\n5. Call the REST API directly for writes. The JavaScript SDK 3.0.3 has list, retrieve and search methods only\n\n### dotCMS\n\n1. Search the spec with `search` before writing an `execute` call, and return only the fields you need\n2. Use a token for a dedicated user and role, not an administrator's\n3. Confirm with the user before execute calls that publish, archive or delete content\n4. Keep results small with pick and first, since output is capped at about 25,000 characters\n5. Use download_assets for theme folders so files land on disk instead of in context\n\n## Questions\n\n### Which is better for AI agents, ButterCMS or dotCMS?\n\ndotCMS scores 57.7 (C) on agent readiness against ButterCMS's 51.4 (D), and leads in 5 of 7 scored categories. ButterCMS leads on reliability and schema \u0026 documentation.\n\n### Do ButterCMS and dotCMS need an API key?\n\nBoth need an API key.\n\n### Can an agent call ButterCMS and dotCMS without installing anything?\n\nButterCMS has a hosted endpoint at https://api.buttercms.com/v2. dotCMS runs on your own machine, with no hosted endpoint listed.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/buttercms-vs-dotcms.json, and with the fewest tokens: https://www.anchorterminal.com/compare/buttercms-vs-dotcms.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"buttercms\", \"b\": \"dotcms\"}`. From a terminal: `anchor compare buttercms dotcms`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/buttercms.json and https://www.anchorterminal.com/api/v1/tools/dotcms.json\n\n## Other comparisons with ButterCMS or dotCMS\n\n- [BCMS vs ButterCMS](https://www.anchorterminal.com/compare/bcms-vs-buttercms.md)\n- [BCMS vs dotCMS](https://www.anchorterminal.com/compare/bcms-vs-dotcms.md)\n- [ButterCMS vs Contentstack](https://www.anchorterminal.com/compare/buttercms-vs-contentstack.md)\n- [ButterCMS vs Cosmic](https://www.anchorterminal.com/compare/buttercms-vs-cosmic.md)\n- [ButterCMS vs DatoCMS](https://www.anchorterminal.com/compare/buttercms-vs-datocms.md)\n- [ButterCMS vs Directus](https://www.anchorterminal.com/compare/buttercms-vs-directus.md)\n- [ButterCMS vs Ghost](https://www.anchorterminal.com/compare/buttercms-vs-ghost.md)\n- [ButterCMS vs Hygraph](https://www.anchorterminal.com/compare/buttercms-vs-hygraph.md)\n- [ButterCMS vs Kontent.ai](https://www.anchorterminal.com/compare/buttercms-vs-kontent-ai.md)\n- [ButterCMS vs Payload](https://www.anchorterminal.com/compare/buttercms-vs-payload.md)\n- [ButterCMS vs Prismic](https://www.anchorterminal.com/compare/buttercms-vs-prismic.md)\n- [ButterCMS vs Sanity](https://www.anchorterminal.com/compare/buttercms-vs-sanity.md)\n- [ButterCMS vs Storyblok](https://www.anchorterminal.com/compare/buttercms-vs-storyblok.md)\n- [ButterCMS vs Strapi](https://www.anchorterminal.com/compare/buttercms-vs-strapi.md)\n- [ButterCMS vs Webflow](https://www.anchorterminal.com/compare/buttercms-vs-webflow.md)\n- [ButterCMS vs WordPress](https://www.anchorterminal.com/compare/buttercms-vs-wordpress.md)\n- [Contentstack vs dotCMS](https://www.anchorterminal.com/compare/contentstack-vs-dotcms.md)\n- [Cosmic vs dotCMS](https://www.anchorterminal.com/compare/cosmic-vs-dotcms.md)\n- [DatoCMS vs dotCMS](https://www.anchorterminal.com/compare/datocms-vs-dotcms.md)\n- [Directus vs dotCMS](https://www.anchorterminal.com/compare/directus-vs-dotcms.md)\n- [dotCMS vs Ghost](https://www.anchorterminal.com/compare/dotcms-vs-ghost.md)\n- [dotCMS vs Hygraph](https://www.anchorterminal.com/compare/dotcms-vs-hygraph.md)\n- [dotCMS vs Kontent.ai](https://www.anchorterminal.com/compare/dotcms-vs-kontent-ai.md)\n- [dotCMS vs Payload](https://www.anchorterminal.com/compare/dotcms-vs-payload.md)\n- [dotCMS vs Prismic](https://www.anchorterminal.com/compare/dotcms-vs-prismic.md)\n- [dotCMS vs Sanity](https://www.anchorterminal.com/compare/dotcms-vs-sanity.md)\n- [dotCMS vs Storyblok](https://www.anchorterminal.com/compare/dotcms-vs-storyblok.md)\n- [dotCMS vs Strapi](https://www.anchorterminal.com/compare/dotcms-vs-strapi.md)\n- [dotCMS vs Webflow](https://www.anchorterminal.com/compare/dotcms-vs-webflow.md)\n- [dotCMS vs WordPress](https://www.anchorterminal.com/compare/dotcms-vs-wordpress.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": "ButterCMS vs dotCMS", "url": "" } ], "description": "dotCMS scores 57.7 (C) to ButterCMS's 51.4 (D) for content management. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "ButterCMS D 51.4", "dotCMS C 57.7", "scores" ], "h1": "ButterCMS vs dotCMS", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/buttercms-vs-dotcms", "published": "2026-10-01", "section": "tools", "title": "ButterCMS vs dotCMS for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/buttercms-vs-dotcms" }, "tokens": { "markdown": 4200, "slim": 2280 }, "version": 1 }