{ "data": { "similar": [ { "grade": "BB", "json": "https://www.anchorterminal.com/tools/datocms.json", "name": "DatoCMS", "score": 74.4, "shared": [ "cms.content", "cms.publish", "cms.assets", "cms.localisation" ], "slug": "datocms" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/sanity.json", "name": "Sanity", "score": 73.7, "shared": [ "cms.content", "cms.publish", "cms.assets", "cms.localisation" ], "slug": "sanity" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/kontent-ai.json", "name": "Kontent.ai", "score": 70.5, "shared": [ "cms.content", "cms.publish", "cms.assets", "cms.localisation" ], "slug": "kontent-ai" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/webflow.json", "name": "Webflow", "score": 69.4, "shared": [ "cms.content", "cms.publish", "cms.assets", "cms.localisation" ], "slug": "webflow" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/hygraph.json", "name": "Hygraph", "score": 69.3, "shared": [ "cms.content", "cms.publish", "cms.assets", "cms.localisation" ], "slug": "hygraph" }, { "grade": "B", "json": "https://www.anchorterminal.com/tools/storyblok.json", "name": "Storyblok", "score": 67.7, "shared": [ "cms.content", "cms.publish", "cms.assets", "cms.localisation" ], "slug": "storyblok" } ], "tool": { "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", "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": 53.3, "grade": "D", "agentReady": false, "rank": 711, "ranked": true, "rankOf": 950, "categoryRank": 14, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 64, "maintenance": 27, "payments": 20, "reliability": 83, "schema": 78, "security": 36, "transparency": 51 }, "pending": [ "performance", "tasks" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 83, "points": 16.6, "reason": "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 9 October 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). Free and trial accounts get a 429 that the docs say may carry `Retry-After`, and the docs show backoff for 5xx errors. There are no idempotency keys, and the advice for writes is to check that content exists before retrying a create (8 of 15). The pricing page lists an SLA on Enterprise with no figure (5). The v2 API is generally available (10)." }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 78, "points": 12.68, "reason": "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 25 operations (25). A docs llms.txt and a Markdown copy of every docs page (10). All 25 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)." }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 64, "points": 10.4, "reason": "Responses are sized with `page_size`, a `fields` selection, `exclude_body` on posts and `levels` for reference depth (20 of 25). Page and offset pagination with `meta.count`, filters on field values and `order` (20). Errors are documented with causes, but bodies come in three shapes (`detail`, a field map, `error`) with no stable codes, and a write answers 202 with `status: pending` and no identifier, so the result has to be read back (11 of 20). No idempotency keys. Page and post slugs are unique, which limits duplicates, and collection items have no such guard (4 of 20). Writes default to draft, but page creation needs every field key of the page type. Ten SDKs are listed and the docs say to call REST for writes (9 of 15)." }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 36, "points": 6.3, "reason": "One read token and one write token per account, with no scopes, and the docs say rotation is done by contacting support (15 of 30). We took 5 off, not the checklist's 10, because only the read token can travel in the query string. That token also returns drafts with `preview=1` (10). 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 disclosure address at security@buttercms.com and penetration tests described on the security page. No security.txt, no bug bounty, and the certifications listed are those of the AWS and Heroku data centres (7 of 20)." }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 20, "points": 2.5, "reason": "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)." }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 27, "points": 2.36, "reason": "No dated API changelog was found. The docs sitemap shows the Write API reference pages last modified on 9 September 2026, and the SDKs are older, with `buttercms` 3.0.3 tagged on 4 September 2025 and `buttercms-python` 2.1.1 on 7 May 2024. We scored the recency line 10 of 30 on the docs dates. A strict reading on releases gives 0. 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, the two we read are over a year old, and the official MCP registry has no ButterCMS entry (7 of 15). 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)." }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 51, "points": 4.46, "note": "editorial 26, provenance 76", "reason": "Closed service, MIT SDKs. The only published contract is an undated website Terms of Service that names no legal entity and has passages about collaborating on legal documents that do not describe a CMS (8 of 30). The privacy policy, last modified 15 August 2022, covers the website and says nothing about content stored in the CMS. The security page says data is kept as long as the customer needs it, the docs give 30 or more days for backups, and a DPA is on request for Enterprise customers (10 of 30). No deprecation policy or dated notice was found. PUT on pages is kept for backwards compatibility (2 of 20). Heroku, AWS, Fastly, Stripe and TinyMCE are named across the security page and docs. No sub-processor list or hosting region is published (6 of 20)." } ], "assessment": { "date": "2026-10-09", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "Responses are sized with `page_size`, a `fields` selection, `exclude_body` on posts and `levels` for reference depth (20 of 25). Page and offset pagination with `meta.count`, filters on field values and `order` (20). Errors are documented with causes, but bodies come in three shapes (`detail`, a field map, `error`) with no stable codes, and a write answers 202 with `status: pending` and no identifier, so the result has to be read back (11 of 20). No idempotency keys. Page and post slugs are unique, which limits duplicates, and collection items have no such guard (4 of 20). Writes default to draft, but page creation needs every field key of the page type. Ten SDKs are listed and the docs say to call REST for writes (9 of 15).", "maintenance": "No dated API changelog was found. The docs sitemap shows the Write API reference pages last modified on 9 September 2026, and the SDKs are older, with `buttercms` 3.0.3 tagged on 4 September 2025 and `buttercms-python` 2.1.1 on 7 May 2024. We scored the recency line 10 of 30 on the docs dates. A strict reading on releases gives 0. 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, the two we read are over a year old, and the official MCP registry has no ButterCMS entry (7 of 15). 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).", "payments": "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).", "reliability": "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 9 October 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). Free and trial accounts get a 429 that the docs say may carry `Retry-After`, and the docs show backoff for 5xx errors. There are no idempotency keys, and the advice for writes is to check that content exists before retrying a create (8 of 15). The pricing page lists an SLA on Enterprise with no figure (5). The v2 API is generally available (10).", "schema": "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 25 operations (25). A docs llms.txt and a Markdown copy of every docs page (10). All 25 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).", "security": "One read token and one write token per account, with no scopes, and the docs say rotation is done by contacting support (15 of 30). We took 5 off, not the checklist's 10, because only the read token can travel in the query string. That token also returns drafts with `preview=1` (10). 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 disclosure address at security@buttercms.com and penetration tests described on the security page. No security.txt, no bug bounty, and the certifications listed are those of the AWS and Heroku data centres (7 of 20).", "transparency": "Closed service, MIT SDKs. The only published contract is an undated website Terms of Service that names no legal entity and has passages about collaborating on legal documents that do not describe a CMS (8 of 30). The privacy policy, last modified 15 August 2022, covers the website and says nothing about content stored in the CMS. The security page says data is kept as long as the customer needs it, the docs give 30 or more days for backups, and a DPA is on request for Enterprise customers (10 of 30). No deprecation policy or dated notice was found. PUT on pages is kept for backwards compatibility (2 of 20). Heroku, AWS, Fastly, Stripe and TinyMCE are named across the security page and docs. No sub-processor list or hosting region is published (6 of 20)." }, "sources": [ { "what": "robots.txt", "url": "https://buttercms.com/robots.txt", "seen": "2026-10-09" }, { "what": "site llms.txt", "url": "https://buttercms.com/llms.txt", "seen": "2026-10-09" }, { "what": "docs index llms.txt", "url": "https://buttercms.com/docs/llms.txt", "seen": "2026-10-09" }, { "what": "API overview", "url": "https://buttercms.com/docs/api/overview", "seen": "2026-10-09" }, { "what": "OpenAPI, whole API", "url": "https://buttercms.com/docs/api/openapi/openapi.yaml", "seen": "2026-10-09" }, { "what": "OpenAPI, Write API", "url": "https://buttercms.com/docs/api/openapi/write_api.yaml", "seen": "2026-10-09" }, { "what": "authentication and API tokens", "url": "https://buttercms.com/docs/api/concepts/authentication-api-tokens.md", "seen": "2026-10-09" }, { "what": "API tokens, dashboard guide", "url": "https://buttercms.com/docs/create-content/authentication/api-tokens.md", "seen": "2026-10-09" }, { "what": "rate limits and throttling", "url": "https://buttercms.com/docs/api/concepts/rate-limits-throttling.md", "seen": "2026-10-09" }, { "what": "HTTP status codes and errors", "url": "https://buttercms.com/docs/api/concepts/http-status-codes-errors.md", "seen": "2026-10-09" }, { "what": "request and response format", "url": "https://buttercms.com/docs/api/concepts/request-response-format.md", "seen": "2026-10-09" }, { "what": "API architecture", "url": "https://buttercms.com/docs/api/concepts/api-architecture-principles.md", "seen": "2026-10-09" }, { "what": "bulk operations", "url": "https://buttercms.com/docs/api/concepts/bulk-operations.md", "seen": "2026-10-09" }, { "what": "usage and limits", "url": "https://buttercms.com/docs/build-your-app/performance/usage-limits.md", "seen": "2026-10-09" }, { "what": "integration with AI tools", "url": "https://buttercms.com/docs/build-your-app/third-party-integrations/ai-tools-integration.md", "seen": "2026-10-09" }, { "what": "SDKs overview", "url": "https://buttercms.com/docs/frameworks/sdks/overview.md", "seen": "2026-10-09" }, { "what": "JavaScript SDK docs", "url": "https://buttercms.com/docs/frameworks/sdks/javascript-sdk.md", "seen": "2026-10-09" }, { "what": "security overview", "url": "https://buttercms.com/docs/build-your-app/security-compliance/security-overview.md", "seen": "2026-10-09" }, { "what": "compliance certifications", "url": "https://buttercms.com/docs/build-your-app/security-compliance/compliance-certifications.md", "seen": "2026-10-09" }, { "what": "data protection and encryption", "url": "https://buttercms.com/docs/build-your-app/security-compliance/data-protection-encryption.md", "seen": "2026-10-09" }, { "what": "infrastructure and hosting", "url": "https://buttercms.com/docs/build-your-app/security-compliance/infrastructure-hosting.md", "seen": "2026-10-09" }, { "what": "revision history retention", "url": "https://buttercms.com/docs/create-content/versioning-history/retention-policies.md", "seen": "2026-10-09" }, { "what": "custom roles and permissions", "url": "https://buttercms.com/docs/create-content/collaborating-with-teams/custom-roles-permissions.md", "seen": "2026-10-09" }, { "what": "docs sitemap, page modification dates", "url": "https://buttercms.com/docs/sitemap.xml", "seen": "2026-10-09" }, { "what": "pricing", "url": "https://buttercms.com/pricing/", "seen": "2026-10-09" }, { "what": "terms of service", "url": "https://buttercms.com/terms/", "seen": "2026-10-09" }, { "what": "privacy policy", "url": "https://buttercms.com/privacy/", "seen": "2026-10-09" }, { "what": "security page", "url": "https://buttercms.com/security/", "seen": "2026-10-09" }, { "what": "security.txt (404)", "url": "https://buttercms.com/.well-known/security.txt", "seen": "2026-10-09" }, { "what": "status page", "url": "https://status.buttercms.com/", "seen": "2026-10-09" }, { "what": "status history feed", "url": "https://status.buttercms.com/history.rss", "seen": "2026-10-09" }, { "what": "GitHub organisation", "url": "https://github.com/buttercms", "seen": "2026-10-09" }, { "what": "JavaScript SDK repository, cloned", "url": "https://github.com/ButterCMS/buttercms-js", "seen": "2026-10-09" }, { "what": "Python SDK repository, cloned", "url": "https://github.com/ButterCMS/buttercms-python", "seen": "2026-10-09" }, { "what": "npm registry, buttercms", "url": "https://registry.npmjs.org/buttercms/latest", "seen": "2026-10-09" }, { "what": "npm weekly downloads", "url": "https://api.npmjs.org/downloads/point/last-week/buttercms", "seen": "2026-10-09" }, { "what": "RDAP, buttercms.com", "url": "https://rdap.verisign.com/com/v1/domain/buttercms.com", "seen": "2026-10-09" }, { "what": "official MCP registry search", "url": "https://registry.modelcontextprotocol.io/v0/servers?search=butter", "seen": "2026-10-09" } ], "openQuestions": [ "Not established what the Write API add-on costs. The pricing page lists it without a price and the docs send buyers to the billing screen or support", "Not established whether the 14-day trial or the Free plan can get a write token. The pricing page lists the add-on only from Advanced upwards", "Not established whether ButterCMS holds a SOC 2 report of its own. The docs table marks SOC 2 Type 2 as compliant and says Enterprise customers can request reports, and the same page attributes the certifications to AWS data centres", "Not established how a failed background write is reported after a 202 answer", "Not established which legal entity contracts with customers today. The privacy policy names ButterCMS LLC and a status post says Tiugo Technologies acquired ButterCMS in 2024", "unchecked: GitHub star counts, open issues and whether CI passes on the SDK repositories", "unchecked: the eight SDKs other than JavaScript and Python, and PyPI download figures", "unchecked: the 401 and 429 response bodies and headers. We sent no request to api.buttercms.com beyond robots.txt", "unchecked: the signup flow at app.buttercms.com, so no card on the Free plan rests on the pricing page", "The terms and privacy links point at website documents because the vendor publishes no service agreement or product privacy notice. The Write API's OpenAPI file names the terms page as its licence", "The lead was right that the API reads and writes. It did not say that the Write API is a paid add-on from the Advanced plan with a monthly cap" ] }, "negative": -2, "negativeNotes": [ "9 October 2026. The docs page on AI tools shows `butter.page.update(...)` as the way to write through the JavaScript SDK. The published SDK 3.0.3 has list, retrieve and search methods only, and the SDK overview says to call REST for writes (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, support rotates tokens, and the terms are an undated website document.", "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 (25 operations, 328 examples), 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. The JavaScript SDK's last release was 3.0.3 on 4 September 2025 and it 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.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53.3 } ], "editorialScores": { "ergonomics": 64, "maintenance": 27, "payments": 20, "reliability": 83, "schema": 78, "security": 36, "transparency": 26 }, "provenanceScore": 76 }, "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" }, "notable": [ "The Write API has nine operations at https://api.buttercms.com/v2, create and update for pages, create, full update, partial update and delete for collection items, and create, update and delete for blog posts (https://buttercms.com/docs/api/openapi/write_api.yaml)", "The pricing page lists the Write API as an add-on on Advanced (up to 2,000 write calls a month) and Professional (up to 5,000), and as included on Enterprise with a custom limit. Free and Basic do not list it (https://buttercms.com/pricing/)", "One docs page says to buy the add-on under Settings, Billing, and another says to contact support to enable a write token, which needs verification (https://buttercms.com/docs/api/concepts/authentication-api-tokens.md, https://buttercms.com/docs/create-content/authentication/api-tokens.md)", "Write calls return 202 Accepted with `{\"status\": \"pending\"}` while media upload, validation and webhooks run in the background (https://buttercms.com/docs/api/concepts/http-status-codes-errors.md)", "Limits are monthly quotas, 50,000 API calls on Free up to 1M on Professional. Free and trial accounts get a 429 at the limit, and paid plans are not blocked. No per-second limit is published (https://buttercms.com/docs/api/concepts/rate-limits-throttling.md)", "Page types must be built in the dashboard first. The create-page description says new page types cannot be created through the API, and scheduling is not supported through the Write API for pages (https://buttercms.com/docs/api/openapi/write_api.yaml)", "The docs page on AI tools has an example calling `butter.page.update`, and the published JavaScript SDK 3.0.3 has no update method (https://buttercms.com/docs/build-your-app/third-party-integrations/ai-tools-integration.md, https://github.com/ButterCMS/buttercms-js)", "A status page post of September 2024 says ButterCMS was acquired by Tiugo Technologies. The privacy policy still names ButterCMS LLC (https://status.buttercms.com/history.rss)", "No MCP server was found in the docs index, and the official MCP registry has no ButterCMS entry (https://buttercms.com/docs/llms.txt, https://registry.modelcontextprotocol.io/v0/servers?search=butter)" ], "area": "business", "details": [ { "label": "Surfaces", "value": "REST Read API (16 GET operations) and REST Write API (9 operations) at https://api.buttercms.com/v2, webhooks for page, post, collection and media events, and an Image API on the CDN. No MCP server or CLI found" }, { "label": "Write API", "value": "Pages: create (POST) and update (PATCH, with PUT kept for backwards compatibility). Collection items: create, PUT, PATCH, DELETE. Blog posts: create, PATCH, DELETE. No page delete, no page type or collection schema operations, no media library endpoint, no version or restore operation" }, { "label": "Credentials", "value": "One read token and one write token per account. Read token as `auth_token` in the query string or `Authorization: Token \u003ctoken\u003e`. Write token in the header only. Rotation by contacting support, per the docs" }, { "label": "Write access", "value": "Paid add-on. Advanced up to 2,000 write calls a month, Professional up to 5,000, Enterprise custom. Add-on price not published" }, { "label": "Plans", "value": "Free $0 (50,000 API calls a month, 5 pages, 50 blog posts, 50 collection items, 500 assets). Basic $79 a month or $71 billed yearly (100,000 calls). Advanced $249 or $224 (500,000 calls). Professional $399 or $359 (1M calls, 3 locales). Enterprise through sales. Every plan has unlimited users and a 14-day trial" }, { "label": "Limits", "value": "Monthly API call quotas by plan. Free and trial accounts get 429 with the body `API Calls limit reached.` and, per the docs, possibly a `Retry-After` header counting to the monthly reset. Paid plans are not blocked for overage. No per-second limit published" }, { "label": "Drafts and publishing", "value": "`status` is `draft` by default and `published` publishes at once. Drafts are read with `preview=1`. Blog post updates accept a `scheduled` field. Page scheduling is dashboard only. Version history and restore are in the dashboard" }, { "label": "Assets", "value": "A media field takes a URL, or an object with `url` and `alt`, and the file is downloaded into the media library. Blog posts take `upload_images_to_media_library` for images in the body" }, { "label": "Localisation", "value": "`locale` query parameter, or a `fields` object keyed by locale code to write several locales in one request. Locales must be configured in the account first. 3 locales on Professional, custom on Enterprise, none on lower plans" }, { "label": "Pagination and sizing", "value": "`page` and `page_size`, or `limit` and `offset`, with `meta.count` and next and previous values. `fields` filters and selection, `order`, `exclude_body` on posts and `levels` (1 to 5) for reference depth" }, { "label": "Errors", "value": "JSON bodies in three shapes: `detail` for most errors, a map of field names to messages for validation, and `error` for plan limits. Statuses 400, 401, 403, 404, 405, 429 and 500 are documented with causes" }, { "label": "Webhooks", "value": "Events for pages, blog posts, collection items and media. The docs index describes delivery as best effort without retries, and endpoints must answer within 5 seconds" }, { "label": "SDKs", "value": "Ten listed (JavaScript, Python, Ruby, PHP, Java, .NET, Go, Dart, Swift, Kotlin), MIT. The docs say to use the REST API for writes. JavaScript `buttercms` 3.0.3 (4 September 2025), Python `buttercms-python` 2.1.1 (7 May 2024)" }, { "label": "Roles and audit", "value": "Dashboard roles, 2 on Free and Basic, 3 on Advanced and Professional, custom on Enterprise. Audit logs and access logs are listed as Enterprise functions. API tokens are not tied to a role in the reviewed docs" }, { "label": "Security claims", "value": "AES-256 at rest, TLS 1.2, daily backups kept 30+ days, SAML single sign-on, penetration tests. The certifications listed (ISO 27001, SOC 2 Type 2 and others) are those of the AWS and Heroku data centres. Reports go to security@buttercms.com" }, { "label": "Hosting", "value": "Heroku and AWS, with Fastly as CDN and Stripe for payments. No region or sub-processor list published" }, { "label": "Status", "value": "status.buttercms.com on Atlassian Statuspage with CDN, API and Login Page components. Latest incidents: two on 20 October 2025 and an API, login and dashboard outage of about an hour on 24 September 2025" }, { "label": "Open source", "value": "No. The docs call the platform closed-source. SDKs and starter projects are MIT" } ], "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": 76, "checks": [ { "check": "Legal entity named", "value": "ButterCMS LLC", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "buttercms.com, registered 2015-03-24 (11 years)", "points": 15, "max": 15, "state": "ok" }, { "check": "Endpoint on the vendor's domain", "value": "api.buttercms.com", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "read, states 4 of the 7 things a reader expects", "points": 7.4, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "read, states 6 of the 8 things a reader expects", "points": 8.5, "max": 10, "state": "part" }, { "check": "Status page", "value": "status.buttercms.com", "points": 10, "max": 10, "state": "ok" }, { "check": "Changelog", "value": "not found", "points": 0, "max": 10, "state": "no" }, { "check": "security.txt", "value": "not found", "points": 0, "max": 10, "state": "no" } ], "policies": [ { "kind": "terms", "url": "https://buttercms.com/terms/", "state": "read", "readAt": "2026-10-09", "words": 2765, "points": 7.4, "max": 10, "expected": [ { "key": "terms.date", "label": "Gives the date it was last updated", "found": false }, { "key": "terms.law", "label": "Names the governing law or courts", "found": true, "quote": "These Terms of Service and any dispute or claim arising out of, or related to them, shall be governed by and construed in accordance with the internal laws of the State of Michigan without giving effect to any choice or conflict of law provision or rule.", "says": "The law of the State of Michigan" }, { "key": "terms.liability", "label": "States a limit on its liability", "found": true, "quote": "We are not liable for damages, direct or consequential, resulting from your use of the Website, and you agree to defend, indemnify, and hold us harmless from any claims, losses, liability costs, and expenses (including but not limited to attorney's fees) arising from your violation of any third-party's rights.", "says": "Rules out indirect and consequential losses, with no cap named in this sentence" }, { "key": "terms.termination", "label": "Says how the agreement or account can be ended", "found": true, "quote": "We also reserve the right to suspend or restrict access to some features to users." }, { "key": "terms.changes", "label": "Says how changes to the terms are announced", "found": false }, { "key": "terms.use", "label": "Lists what users may not do", "found": true, "quote": "So you agree not to copy, modify, create derivative works of, publicly display, publicly perform, republish, any of our copyrighted material, except to the extent permitted by the Website itself." }, { "key": "terms.sla", "label": "Refers to a service level or uptime commitment", "found": false } ], "toKnow": [ { "key": "terms.cutoff", "label": "Says access can be ended without notice or for any reason", "found": true, "quote": "As is customary for internet websites, we reserve the right to disable any user account, at any time in our sole discretion, for any or no reason, including, if in our opinion, you have failed to comply with any provision of these Terms of Service." } ], "notes": [ { "date": "2026-10-08", "text": "ButterCMS reserves the right to remove, edit or modify any content at its sole discretion, at any time, without notice and for any reason.", "quote": "We reserve the right to, but do not have any obligation to, (i) remove, edit or modify any Content in our sole discretion, at any time, without notice to you and for any reason" }, { "date": "2026-10-08", "text": "The terms say ButterCMS is not liable for damages, direct or consequential, resulting from use of the Website.", "quote": "We are not liable for damages, direct or consequential, resulting from your use of the Website" }, { "date": "2026-10-08", "text": "ButterCMS may change pricing and add new charges at the end of the initial or current renewal term on 30 days' prior notice.", "quote": "ButterCMS reserves the right to change the pricing and institute new charges and pricing at the end of the Initial Service Term or the current renewal term, upon thirty (30) days' prior notice." } ] }, { "kind": "privacy", "url": "https://buttercms.com/privacy/", "state": "read", "readAt": "2026-10-09", "statedDate": "2022-08-15", "words": 2268, "points": 8.5, "max": 10, "expected": [ { "key": "privacy.date", "label": "Gives the date it was last updated", "found": true, "quote": "Last modified: August 15, 2022", "says": "Last updated 2022-08-15" }, { "key": "privacy.collected", "label": "Says what personal data is collected", "found": true, "quote": "This policy describes the types of information we may collect from you or that you may provide when you visit the website www.buttercms.com (our \"Website\") and our practices for collecting, using, maintaining, protecting, and disclosing that information." }, { "key": "privacy.retention", "label": "Says how long data is kept", "found": false }, { "key": "privacy.processors", "label": "Says who else receives the data", "found": true, "quote": "We (or service providers on our behalf) may then send communications and marketing to these email or home addresses." }, { "key": "privacy.sale", "label": "Says whether personal data is sold or shared for advertising", "found": true, "quote": "California residents under 16 years of age may have additional rights regarding the collection and sale of their personal information." }, { "key": "privacy.rights", "label": "Says what rights people have over their data", "found": true, "quote": "To learn more about California residents' privacy rights, visit https://oag.ca.gov/privacy/ccpa" }, { "key": "privacy.contact", "label": "Gives a privacy contact", "found": true, "quote": "To ask questions or comment about this privacy policy and our privacy practices, contact us at: support@buttercms.com", "says": "support@buttercms.com" }, { "key": "privacy.transfers", "label": "Says where data is transferred or stored", "found": false } ], "toKnow": [ { "key": "old", "label": "Has not been updated for three years or more", "found": true, "quote": "Last modified: August 15, 2022" } ], "notes": [ { "date": "2026-10-08", "text": "Online data partners or vendors may link website visits and logins to other personal information, including an email or home address, which may then receive marketing.", "quote": "When you visit or log in to our website, cookies and similar technologies may be used by our online data partners or vendors to associate these activities with other personal information they or others have about you, including by association with your email or home address." } ] } ] }, "pageJsonUrl": "https://www.anchorterminal.com/tools/buttercms.json", "live": { "slug": "buttercms", "probe": { "target": "https://api.buttercms.com/v2", "method": "get", "lastAt": "2026-10-10T02:07:04.45233745Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "too many redirects", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 107, "samples30d": 107, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 0 }, { "date": "2026-10-10", "probes": 22, "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-10-10T02:05:41.70225143Z" }, "versions": [ { "registry": "github", "name": "ButterCMS/buttercms-js", "version": "v3.0.3", "released": "2025-09-04", "seenAt": "2026-10-09T16:44:18.698940824Z" }, { "registry": "npm", "name": "buttercms", "version": "3.0.3", "seenAt": "2026-10-09T16:44:17.650332238Z" }, { "registry": "pypi", "name": "buttercms-python", "version": "2.1.1", "released": "2024-05-07", "seenAt": "2026-10-09T16:44:18.477928122Z" } ], "githubStars": 164, "npmWeekly": 6929, "pypiWeekly": 1093, "pages": [ { "url": "https://buttercms.com/pricing/", "kind": "pricing", "status": 200, "checkedAt": "2026-10-09T18:33:26.750327748Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "9ba825b44b86" }, { "url": "https://buttercms.com/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-10-09T18:33:29.190691009Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "908b6461f1b9" }, { "url": "https://buttercms.com/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-10-09T18:33:31.259657517Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8862b63c94a5" } ], "updatedAt": "2026-10-10T02:07:04.45233745Z" } }, "verify": { "accepts": "a page on buttercms.com or one of its subdomains, or the README of github.com/ButterCMS/buttercms-js", "badgeUrl": "https://www.anchorterminal.com/badges/buttercms.svg", "body": { "slug": "buttercms", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/buttercms", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/buttercms\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/buttercms.svg\" alt=\"ButterCMS on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![ButterCMS on Anchor Terminal](https://www.anchorterminal.com/badges/buttercms.svg)](https://www.anchorterminal.com/tools/buttercms)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/buttercms\"\u003eButterCMS on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/buttercms", "json": "https://www.anchorterminal.com/tools/buttercms.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/buttercms.md", "slim": "https://www.anchorterminal.com/tools/buttercms.min.md" }, "markdown": "## Overview\n\n**Grade D · 53.3/100 · rank #711 of 950 · #14 in CMS \u0026 website publishing · not agent-ready · confidence medium**\n\n\n## Assessment\n\nThe 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, support rotates tokens, and the terms are an undated website document.\n\n## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | ButterCMS LLC (https://buttercms.com) |\n| Kind | HTTP API |\n| Category | CMS \u0026 website publishing (https://www.anchorterminal.com/categories/cms) |\n| Transport | HTTP |\n| Endpoint | `https://api.buttercms.com/v2` |\n| Auth | API key · 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. |\n| Pricing | Freemium ($79 / mo) · 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). |\n| x402 | No · No x402, MPP or L402 in the API docs, the OpenAPI files or the pricing page (checked 2026-10-09). |\n| Licence | Proprietary service under ButterCMS's terms of service. The SDKs and starter projects on GitHub are MIT |\n| Packages | npm: `buttercms`; pypi: `buttercms-python` |\n| Source | https://github.com/ButterCMS/buttercms-js |\n| Docs | https://buttercms.com/docs/api/overview |\n| llms.txt | https://buttercms.com/docs/llms.txt |\n| Last release | 2025-09-04 |\n| npm downloads / week | 6,929 |\n| Surfaces | REST Read API (16 GET operations) and REST Write API (9 operations) at https://api.buttercms.com/v2, webhooks for page, post, collection and media events, and an Image API on the CDN. No MCP server or CLI found |\n| Write API | Pages: create (POST) and update (PATCH, with PUT kept for backwards compatibility). Collection items: create, PUT, PATCH, DELETE. Blog posts: create, PATCH, DELETE. No page delete, no page type or collection schema operations, no media library endpoint, no version or restore operation |\n| Credentials | One read token and one write token per account. Read token as `auth_token` in the query string or `Authorization: Token \u003ctoken\u003e`. Write token in the header only. Rotation by contacting support, per the docs |\n| Write access | Paid add-on. Advanced up to 2,000 write calls a month, Professional up to 5,000, Enterprise custom. Add-on price not published |\n| Plans | Free $0 (50,000 API calls a month, 5 pages, 50 blog posts, 50 collection items, 500 assets). Basic $79 a month or $71 billed yearly (100,000 calls). Advanced $249 or $224 (500,000 calls). Professional $399 or $359 (1M calls, 3 locales). Enterprise through sales. Every plan has unlimited users and a 14-day trial |\n| Limits | Monthly API call quotas by plan. Free and trial accounts get 429 with the body `API Calls limit reached.` and, per the docs, possibly a `Retry-After` header counting to the monthly reset. Paid plans are not blocked for overage. No per-second limit published |\n| Drafts and publishing | `status` is `draft` by default and `published` publishes at once. Drafts are read with `preview=1`. Blog post updates accept a `scheduled` field. Page scheduling is dashboard only. Version history and restore are in the dashboard |\n| Assets | A media field takes a URL, or an object with `url` and `alt`, and the file is downloaded into the media library. Blog posts take `upload_images_to_media_library` for images in the body |\n| Localisation | `locale` query parameter, or a `fields` object keyed by locale code to write several locales in one request. Locales must be configured in the account first. 3 locales on Professional, custom on Enterprise, none on lower plans |\n| Pagination and sizing | `page` and `page_size`, or `limit` and `offset`, with `meta.count` and next and previous values. `fields` filters and selection, `order`, `exclude_body` on posts and `levels` (1 to 5) for reference depth |\n| Errors | JSON bodies in three shapes: `detail` for most errors, a map of field names to messages for validation, and `error` for plan limits. Statuses 400, 401, 403, 404, 405, 429 and 500 are documented with causes |\n| Webhooks | Events for pages, blog posts, collection items and media. The docs index describes delivery as best effort without retries, and endpoints must answer within 5 seconds |\n| SDKs | Ten listed (JavaScript, Python, Ruby, PHP, Java, .NET, Go, Dart, Swift, Kotlin), MIT. The docs say to use the REST API for writes. JavaScript `buttercms` 3.0.3 (4 September 2025), Python `buttercms-python` 2.1.1 (7 May 2024) |\n| Roles and audit | Dashboard roles, 2 on Free and Basic, 3 on Advanced and Professional, custom on Enterprise. Audit logs and access logs are listed as Enterprise functions. API tokens are not tied to a role in the reviewed docs |\n| Security claims | AES-256 at rest, TLS 1.2, daily backups kept 30+ days, SAML single sign-on, penetration tests. The certifications listed (ISO 27001, SOC 2 Type 2 and others) are those of the AWS and Heroku data centres. Reports go to security@buttercms.com |\n| Hosting | Heroku and AWS, with Fastly as CDN and Stripe for payments. No region or sub-processor list published |\n| Status | status.buttercms.com on Atlassian Statuspage with CDN, API and Login Page components. Latest incidents: two on 20 October 2025 and an API, login and dashboard outage of about an hour on 24 September 2025 |\n| Open source | No. The docs call the platform closed-source. SDKs and starter projects are MIT |\n| Capabilities | cms.content, cms.publish, cms.assets, cms.localisation |\n| Tags | official, hosted, closed-source, api-key, openapi, llms-txt, webhooks, free-tier, no-card, status-page, javascript, python, php, ruby |\n| JSON | https://www.anchorterminal.com/api/v1/tools/buttercms.json |\n\n## Score breakdown (methodology v0.4, October 2026 research run)\n\nAssessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 83 | 16.6 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 78 | 12.7 |\n| Agent ergonomics | 13% | 16.2 | 64 | 10.4 |\n| Security \u0026 auth | 14% | 17.5 | 36 | 6.3 |\n| Payments \u0026 pricing | 10% | 12.5 | 20 | 2.5 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 27 | 2.4 |\n| Transparency \u0026 trust (editorial 26, provenance 76) | 7% | 8.8 | 51 | 4.5 |\n| Negative events | up to −15 | up to −15 | 9 October 2026. The docs page on AI tools shows `butter.page.update(...)` as the way to write through the JavaScript SDK. The published SDK 3.0.3 has list, retrieve and search methods only, and the SDK overview says to call REST for writes (https://buttercms.com/docs/build-your-app/third-party-integrations/ai-tools-integration.md, https://github.com/ButterCMS/buttercms-js). 2 points. | -2 |\n| **Total** | | | | **53.3 → D** |\n\n### Why each score\n\n- Reliability 83: 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 9 October 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). Free and trial accounts get a 429 that the docs say may carry `Retry-After`, and the docs show backoff for 5xx errors. There are no idempotency keys, and the advice for writes is to check that content exists before retrying a create (8 of 15). The pricing page lists an SLA on Enterprise with no figure (5). The v2 API is generally available (10).\n- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 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 25 operations (25). A docs llms.txt and a Markdown copy of every docs page (10). All 25 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- Agent ergonomics 64: Responses are sized with `page_size`, a `fields` selection, `exclude_body` on posts and `levels` for reference depth (20 of 25). Page and offset pagination with `meta.count`, filters on field values and `order` (20). Errors are documented with causes, but bodies come in three shapes (`detail`, a field map, `error`) with no stable codes, and a write answers 202 with `status: pending` and no identifier, so the result has to be read back (11 of 20). No idempotency keys. Page and post slugs are unique, which limits duplicates, and collection items have no such guard (4 of 20). Writes default to draft, but page creation needs every field key of the page type. Ten SDKs are listed and the docs say to call REST for writes (9 of 15).\n- Security \u0026 auth 36: One read token and one write token per account, with no scopes, and the docs say rotation is done by contacting support (15 of 30). We took 5 off, not the checklist's 10, because only the read token can travel in the query string. That token also returns drafts with `preview=1` (10). 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 disclosure address at security@buttercms.com and penetration tests described on the security page. No security.txt, no bug bounty, and the certifications listed are those of the AWS and Heroku data centres (7 of 20).\n- Payments \u0026 pricing 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- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 27: No dated API changelog was found. The docs sitemap shows the Write API reference pages last modified on 9 September 2026, and the SDKs are older, with `buttercms` 3.0.3 tagged on 4 September 2025 and `buttercms-python` 2.1.1 on 7 May 2024. We scored the recency line 10 of 30 on the docs dates. A strict reading on releases gives 0. 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, the two we read are over a year old, and the official MCP registry has no ButterCMS entry (7 of 15). 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- Transparency \u0026 trust 51: Closed service, MIT SDKs. The only published contract is an undated website Terms of Service that names no legal entity and has passages about collaborating on legal documents that do not describe a CMS (8 of 30). The privacy policy, last modified 15 August 2022, covers the website and says nothing about content stored in the CMS. The security page says data is kept as long as the customer needs it, the docs give 30 or more days for backups, and a DPA is on request for Enterprise customers (10 of 30). No deprecation policy or dated notice was found. PUT on pages is kept for backwards compatibility (2 of 20). Heroku, AWS, Fastly, Stripe and TinyMCE are named across the security page and docs. No sub-processor list or hosting region is published (6 of 20).\n\nFix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (23 items): https://www.anchorterminal.com/fixes/buttercms.md (JSON https://www.anchorterminal.com/fixes/buttercms.json)\n\n### What we couldn't check\n\n- Not established what the Write API add-on costs. The pricing page lists it without a price and the docs send buyers to the billing screen or support\n- Not established whether the 14-day trial or the Free plan can get a write token. The pricing page lists the add-on only from Advanced upwards\n- Not established whether ButterCMS holds a SOC 2 report of its own. The docs table marks SOC 2 Type 2 as compliant and says Enterprise customers can request reports, and the same page attributes the certifications to AWS data centres\n- Not established how a failed background write is reported after a 202 answer\n- Not established which legal entity contracts with customers today. The privacy policy names ButterCMS LLC and a status post says Tiugo Technologies acquired ButterCMS in 2024\n- unchecked: GitHub star counts, open issues and whether CI passes on the SDK repositories\n- unchecked: the eight SDKs other than JavaScript and Python, and PyPI download figures\n- unchecked: the 401 and 429 response bodies and headers. We sent no request to api.buttercms.com beyond robots.txt\n- unchecked: the signup flow at app.buttercms.com, so no card on the Free plan rests on the pricing page\n- The terms and privacy links point at website documents because the vendor publishes no service agreement or product privacy notice. The Write API's OpenAPI file names the terms page as its licence\n- The lead was right that the API reads and writes. It did not say that the Write API is a paid add-on from the Advanced plan with a monthly cap\n\n### Sources\n\n- robots.txt: \u003chttps://buttercms.com/robots.txt\u003e (seen 2026-10-09)\n- site llms.txt: \u003chttps://buttercms.com/llms.txt\u003e (seen 2026-10-09)\n- docs index llms.txt: \u003chttps://buttercms.com/docs/llms.txt\u003e (seen 2026-10-09)\n- API overview: \u003chttps://buttercms.com/docs/api/overview\u003e (seen 2026-10-09)\n- OpenAPI, whole API: \u003chttps://buttercms.com/docs/api/openapi/openapi.yaml\u003e (seen 2026-10-09)\n- OpenAPI, Write API: \u003chttps://buttercms.com/docs/api/openapi/write_api.yaml\u003e (seen 2026-10-09)\n- authentication and API tokens: \u003chttps://buttercms.com/docs/api/concepts/authentication-api-tokens.md\u003e (seen 2026-10-09)\n- API tokens, dashboard guide: \u003chttps://buttercms.com/docs/create-content/authentication/api-tokens.md\u003e (seen 2026-10-09)\n- rate limits and throttling: \u003chttps://buttercms.com/docs/api/concepts/rate-limits-throttling.md\u003e (seen 2026-10-09)\n- HTTP status codes and errors: \u003chttps://buttercms.com/docs/api/concepts/http-status-codes-errors.md\u003e (seen 2026-10-09)\n- request and response format: \u003chttps://buttercms.com/docs/api/concepts/request-response-format.md\u003e (seen 2026-10-09)\n- API architecture: \u003chttps://buttercms.com/docs/api/concepts/api-architecture-principles.md\u003e (seen 2026-10-09)\n- bulk operations: \u003chttps://buttercms.com/docs/api/concepts/bulk-operations.md\u003e (seen 2026-10-09)\n- usage and limits: \u003chttps://buttercms.com/docs/build-your-app/performance/usage-limits.md\u003e (seen 2026-10-09)\n- integration with AI tools: \u003chttps://buttercms.com/docs/build-your-app/third-party-integrations/ai-tools-integration.md\u003e (seen 2026-10-09)\n- SDKs overview: \u003chttps://buttercms.com/docs/frameworks/sdks/overview.md\u003e (seen 2026-10-09)\n- JavaScript SDK docs: \u003chttps://buttercms.com/docs/frameworks/sdks/javascript-sdk.md\u003e (seen 2026-10-09)\n- security overview: \u003chttps://buttercms.com/docs/build-your-app/security-compliance/security-overview.md\u003e (seen 2026-10-09)\n- compliance certifications: \u003chttps://buttercms.com/docs/build-your-app/security-compliance/compliance-certifications.md\u003e (seen 2026-10-09)\n- data protection and encryption: \u003chttps://buttercms.com/docs/build-your-app/security-compliance/data-protection-encryption.md\u003e (seen 2026-10-09)\n- infrastructure and hosting: \u003chttps://buttercms.com/docs/build-your-app/security-compliance/infrastructure-hosting.md\u003e (seen 2026-10-09)\n- revision history retention: \u003chttps://buttercms.com/docs/create-content/versioning-history/retention-policies.md\u003e (seen 2026-10-09)\n- custom roles and permissions: \u003chttps://buttercms.com/docs/create-content/collaborating-with-teams/custom-roles-permissions.md\u003e (seen 2026-10-09)\n- docs sitemap, page modification dates: \u003chttps://buttercms.com/docs/sitemap.xml\u003e (seen 2026-10-09)\n- pricing: \u003chttps://buttercms.com/pricing/\u003e (seen 2026-10-09)\n- terms of service: \u003chttps://buttercms.com/terms/\u003e (seen 2026-10-09)\n- privacy policy: \u003chttps://buttercms.com/privacy/\u003e (seen 2026-10-09)\n- security page: \u003chttps://buttercms.com/security/\u003e (seen 2026-10-09)\n- security.txt (404): \u003chttps://buttercms.com/.well-known/security.txt\u003e (seen 2026-10-09)\n- status page: \u003chttps://status.buttercms.com/\u003e (seen 2026-10-09)\n- status history feed: \u003chttps://status.buttercms.com/history.rss\u003e (seen 2026-10-09)\n- GitHub organisation: \u003chttps://github.com/buttercms\u003e (seen 2026-10-09)\n- JavaScript SDK repository, cloned: \u003chttps://github.com/ButterCMS/buttercms-js\u003e (seen 2026-10-09)\n- Python SDK repository, cloned: \u003chttps://github.com/ButterCMS/buttercms-python\u003e (seen 2026-10-09)\n- npm registry, buttercms: \u003chttps://registry.npmjs.org/buttercms/latest\u003e (seen 2026-10-09)\n- npm weekly downloads: \u003chttps://api.npmjs.org/downloads/point/last-week/buttercms\u003e (seen 2026-10-09)\n- RDAP, buttercms.com: \u003chttps://rdap.verisign.com/com/v1/domain/buttercms.com\u003e (seen 2026-10-09)\n- official MCP registry search: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=butter\u003e (seen 2026-10-09)\n\n## Who's behind it (provenance 76/100, checked 2026-10-09)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | ButterCMS LLC | 20/20 |\n| Domain age | buttercms.com, registered 2015-03-24 (11 years) | 15/15 |\n| Endpoint on the vendor's domain | api.buttercms.com | 15/15 |\n| Terms of service | read, states 4 of the 7 things a reader expects | 7.4/10 |\n| Privacy policy | read, states 6 of the 8 things a reader expects | 8.5/10 |\n| Status page | status.buttercms.com | 10/10 |\n| Changelog | not found | 0/10 |\n| security.txt | not found | 0/10 |\n\nThe 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.\n\nThe 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.\n\nThe 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.\n\nA 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.\n\nThe API answers at api.buttercms.com and the dashboard at app.buttercms.com.\n\nbuttercms.com/.well-known/security.txt returns 404. The docs give security@buttercms.com for vulnerability reports.\n\nRDAP for buttercms.com gives a registration date of 2015-03-24 and Amazon Registrar, Inc. as registrar.\n\nNo API changelog was found on the site or in the docs index. The JavaScript SDK repository has a CHANGELOG.md.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://buttercms.com/terms/), read 2026-10-09, gives no date, states 4 of the 7 things a reader expects.\n\n- To know. Says access can be ended without notice or for any reason. \"As is customary for internet websites, we reserve the right to disable any user account, at any time in our sole discretion, for any or no reason, including, if in our opinion, you have failed to comply with any provision of these Terms of Service.\"\n- Not found in the text. Gives the date it was last updated.\n- Names the governing law or courts. The law of the State of Michigan.\n- States a limit on its liability. Rules out indirect and consequential losses, with no cap named in this sentence.\n- Not found in the text. Says how changes to the terms are announced.\n- Not found in the text. Refers to a service level or uptime commitment.\n- Also in the text (2026-10-08). ButterCMS reserves the right to remove, edit or modify any content at its sole discretion, at any time, without notice and for any reason. \"We reserve the right to, but do not have any obligation to, (i) remove, edit or modify any Content in our sole discretion, at any time, without notice to you and for any reason\"\n- Also in the text (2026-10-08). The terms say ButterCMS is not liable for damages, direct or consequential, resulting from use of the Website. \"We are not liable for damages, direct or consequential, resulting from your use of the Website\"\n- Also in the text (2026-10-08). ButterCMS may change pricing and add new charges at the end of the initial or current renewal term on 30 days' prior notice. \"ButterCMS reserves the right to change the pricing and institute new charges and pricing at the end of the Initial Service Term or the current renewal term, upon thirty (30) days' prior notice.\"\n\n**Privacy policy** (https://buttercms.com/privacy/), read 2026-10-09, dated 2022-08-15, states 6 of the 8 things a reader expects.\n\n- To know. Has not been updated for three years or more. \"Last modified: August 15, 2022\"\n- Gives the date it was last updated. Last updated 2022-08-15.\n- Not found in the text. Says how long data is kept.\n- Gives a privacy contact. support@buttercms.com.\n- Not found in the text. Says where data is transferred or stored.\n- Also in the text (2026-10-08). Online data partners or vendors may link website visits and logins to other personal information, including an email or home address, which may then receive marketing. \"When you visit or log in to our website, cookies and similar technologies may be used by our online data partners or vendors to associate these activities with other personal information they or others have about you, including by association with your email or home address.\"\n\n## Live (updated 2026-10-10 02:07 UTC)\n\n- Right now: down, n/a, checked 2026-10-10 02:07 UTC (get on `https://api.buttercms.com/v2`)\n- Uptime 24h 0.0% (107 probes) · 30 days 0.0% (107 probes) · p50 n/a · p95 n/a\n- Vendor status page: none, All Systems Operational\n- github `ButterCMS/buttercms-js` v3.0.3, released 2025-09-04\n- npm `buttercms` 3.0.3\n- pypi `buttercms-python` 2.1.1, released 2024-05-07\n- Watching pricing \u003chttps://buttercms.com/pricing/\u003e\n- Watching privacy \u003chttps://buttercms.com/privacy/\u003e\n- Watching terms \u003chttps://buttercms.com/terms/\u003e\n- Always current: https://www.anchorterminal.com/api/v1/live/buttercms.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Prices\n\n| Item | Price | Unit | Note |\n| --- | --- | --- | --- |\n| Basic | $79 | per month (plan) | billed monthly, $71 billed yearly, 100,000 API calls, no Write API |\n| Advanced | $249 | per month (plan) | billed monthly, $224 billed yearly, 500,000 API calls, Write API add-on priced separately (up to 2,000 write calls) |\n| Professional | $399 | per month (plan) | billed monthly, $359 billed yearly, 1M API calls, Write API add-on priced separately (up to 5,000 write calls) |\n\nAcross all listings: https://www.anchorterminal.com/prices/index.md\n\n## Strengths\n\n- Public OpenAPI 3.1 files for the Read and Write APIs (25 operations, 328 examples), a docs llms.txt and a Markdown copy of every docs page\n- status.buttercms.com lists three components and no incident since 20 October 2025\n- Writes create drafts unless `status` is `published`, and the write token is separate from the read token and accepted only in a header\n- Media fields take a URL and the service copies the file into the media library, so one request creates an entry with its image\n- Free plan with no card and 50,000 API calls a month for reading, and dollar prices for four plans on the pricing page\n\n## Weaknesses\n\n- 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- Create and update calls answer 202 with `{\"status\": \"pending\"}` and no identifier, and there are no idempotency keys\n- One read token and one write token per account, with no scopes. The docs say rotation is done by contacting support\n- Page types and collections cannot be created through the API, pages cannot be deleted through it, and it has no version or rollback operation\n- 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\n- No API changelog or deprecation policy was found. The JavaScript SDK's last release was 3.0.3 on 4 September 2025 and it has no write methods\n\n## Before you call it (notes for agents)\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## Connect\n\nInstall:\n\n```bash\nnpm install buttercms --save\n```\n\nFirst request:\n\n```bash\ncurl -H \"Authorization: Token your_api_token\" \\\n \"https://api.buttercms.com/v2/posts/\"\n```\n\nThrough letme (picks today, calling later): https://letme.dev/buttercms. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| DatoCMS | BB | 74.4 | 71 | cms.content, cms.publish, cms.assets, cms.localisation | no | https://www.anchorterminal.com/tools/datocms.md |\n| Sanity | BB | 73.7 | 84 | cms.content, cms.publish, cms.assets, cms.localisation | no | https://www.anchorterminal.com/tools/sanity.md |\n| Kontent.ai | BB | 70.5 | 153 | cms.content, cms.publish, cms.assets, cms.localisation | no | https://www.anchorterminal.com/tools/kontent-ai.md |\n| Webflow | B | 69.4 | 188 | cms.content, cms.publish, cms.assets, cms.localisation | no | https://www.anchorterminal.com/tools/webflow.md |\n| Hygraph | B | 69.3 | 191 | cms.content, cms.publish, cms.assets, cms.localisation | no | https://www.anchorterminal.com/tools/hygraph.md |\n| Storyblok | B | 67.7 | 244 | cms.content, cms.publish, cms.assets, cms.localisation | no | https://www.anchorterminal.com/tools/storyblok.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- The Write API has nine operations at https://api.buttercms.com/v2, create and update for pages, create, full update, partial update and delete for collection items, and create, update and delete for blog posts (source: \u003chttps://buttercms.com/docs/api/openapi/write_api.yaml\u003e)\n- The pricing page lists the Write API as an add-on on Advanced (up to 2,000 write calls a month) and Professional (up to 5,000), and as included on Enterprise with a custom limit. Free and Basic do not list it (source: \u003chttps://buttercms.com/pricing/\u003e)\n- One docs page says to buy the add-on under Settings, Billing, and another says to contact support to enable a write token, which needs verification (source: \u003chttps://buttercms.com/docs/api/concepts/authentication-api-tokens.md, https://buttercms.com/docs/create-content/authentication/api-tokens.md\u003e)\n- Write calls return 202 Accepted with `{\"status\": \"pending\"}` while media upload, validation and webhooks run in the background (source: \u003chttps://buttercms.com/docs/api/concepts/http-status-codes-errors.md\u003e)\n- Limits are monthly quotas, 50,000 API calls on Free up to 1M on Professional. Free and trial accounts get a 429 at the limit, and paid plans are not blocked. No per-second limit is published (source: \u003chttps://buttercms.com/docs/api/concepts/rate-limits-throttling.md\u003e)\n- Page types must be built in the dashboard first. The create-page description says new page types cannot be created through the API, and scheduling is not supported through the Write API for pages (source: \u003chttps://buttercms.com/docs/api/openapi/write_api.yaml\u003e)\n- The docs page on AI tools has an example calling `butter.page.update`, and the published JavaScript SDK 3.0.3 has no update method (source: \u003chttps://buttercms.com/docs/build-your-app/third-party-integrations/ai-tools-integration.md, https://github.com/ButterCMS/buttercms-js\u003e)\n- A status page post of September 2024 says ButterCMS was acquired by Tiugo Technologies. The privacy policy still names ButterCMS LLC (source: \u003chttps://status.buttercms.com/history.rss\u003e)\n- No MCP server was found in the docs index, and the official MCP registry has no ButterCMS entry (source: \u003chttps://buttercms.com/docs/llms.txt, https://registry.modelcontextprotocol.io/v0/servers?search=butter\u003e)\n\n- #14 of 14 in Best headless CMS and website publishing for AI agents: https://www.anchorterminal.com/best/cms/index.md\n- All 91 cms comparisons: https://www.anchorterminal.com/compare/cms/index.md\n\n## Compare\n\n- [ButterCMS vs Contentstack](https://www.anchorterminal.com/compare/buttercms-vs-contentstack.md): D 53.3 vs B 64\n- [ButterCMS vs DatoCMS](https://www.anchorterminal.com/compare/buttercms-vs-datocms.md): D 53.3 vs BB 74.4\n- [ButterCMS vs Directus](https://www.anchorterminal.com/compare/buttercms-vs-directus.md): D 53.3 vs B 67.1\n- [ButterCMS vs Ghost](https://www.anchorterminal.com/compare/buttercms-vs-ghost.md): D 53.3 vs C 58.3\n- [ButterCMS vs Hygraph](https://www.anchorterminal.com/compare/buttercms-vs-hygraph.md): D 53.3 vs B 69.3\n- [ButterCMS vs Kontent.ai](https://www.anchorterminal.com/compare/buttercms-vs-kontent-ai.md): D 53.3 vs BB 70.5\n- [ButterCMS vs Payload](https://www.anchorterminal.com/compare/buttercms-vs-payload.md): D 53.3 vs C 55.2\n- [ButterCMS vs Prismic](https://www.anchorterminal.com/compare/buttercms-vs-prismic.md): D 53.3 vs C 61.9\n- [ButterCMS vs Sanity](https://www.anchorterminal.com/compare/buttercms-vs-sanity.md): D 53.3 vs BB 73.7\n- [ButterCMS vs Storyblok](https://www.anchorterminal.com/compare/buttercms-vs-storyblok.md): D 53.3 vs B 67.7\n- [ButterCMS vs Strapi](https://www.anchorterminal.com/compare/buttercms-vs-strapi.md): D 53.3 vs B 65.7\n- [ButterCMS vs Webflow](https://www.anchorterminal.com/compare/buttercms-vs-webflow.md): D 53.3 vs B 69.4\n- [ButterCMS vs WordPress](https://www.anchorterminal.com/compare/buttercms-vs-wordpress.md): D 53.3 vs B 64.8\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on buttercms.com or one of its subdomains, or the README of github.com/ButterCMS/buttercms-js. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"buttercms\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/buttercms\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/buttercms.svg\" alt=\"ButterCMS on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![ButterCMS on Anchor Terminal](https://www.anchorterminal.com/badges/buttercms.svg)](https://www.anchorterminal.com/tools/buttercms)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/buttercms\"\u003eButterCMS on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say ButterCMS is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/buttercms-dark.png\n- Light: https://www.anchorterminal.com/assets/share/buttercms-light.png\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-10", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "CMS \u0026 website publishing", "url": "https://www.anchorterminal.com/categories/cms" }, { "name": "ButterCMS", "url": "" } ], "description": "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.", "facts": [ "rank #711 of 950", "API key auth", "0 desk reviews" ], "h1": "ButterCMS", "image": "https://www.anchorterminal.com/assets/og/tools-buttercms.png", "path": "/tools/buttercms", "published": "2026-10-01", "section": "tools", "title": "ButterCMS review (2026): pricing, alternatives and grade D", "toc": null, "updated": "2026-10-10", "url": "https://www.anchorterminal.com/tools/buttercms" }, "tokens": { "markdown": 9000, "slim": 2180 }, "version": 1 }