Head to head · Content management · October 2026 research run
DatoCMS vs Sanity
DatoCMS scores 76.7 (BB) on agent readiness against Sanity's 75.2 (BB), and leads in 2 of 7 scored categories. Sanity leads on reliability, payments & pricing, maintenance & community and transparency & trust. Both do content management.
Best headless CMS and website publishing for AI agents · All 136 cms comparisons
Which one, for what
DatoCMS BB
Best for Teams on DatoCMS who want an agent to create, translate and publish records, upload assets or change models, testing first in a sandbox environment.
Ahead on
- Security & auth, 77 against 67
Also in its favour
- Free to start without a card
- No incidents deducted, where Sanity loses 3 points for them
Watch for
No idempotency keys in the reviewed documentation. Safe retries rest on optimistic locking and the JavaScript client's automatic retry
Sanity BB
Best for Teams that model content as structured documents and want an agent to draft, patch and stage changes in releases for a person to publish.
Ahead on
- Reliability, 87 against 80
- Payments & pricing, 60 against 53
- Maintenance & community, 89 against 81
- Transparency & trust, 87 against 80
Watch for
Schema validation rules run in Sanity Studio and, since October 2026, in MCP writes. The HTTP mutation API accepts a document without checking them
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Security & auth DatoCMS +10
DatoCMS 77
API tokens bound to custom roles, revocable and rotatable by API, sent only as a Bearer header. The MCP server uses OAuth with PKCE S256, dynamic client registration and revocation, with projects and one of three access levels chosen on the consent screen. The OAuth metadata lists three coarse scopes, per the 8 October check, not re-read since because oauth.datocms.com's robots.txt disallows every path (28). Every project starts with a read-only token, roles limit by model, action and environment, and the MCP read-only level is enforced by the runner and by the API through X-Abort-If-Destructive-Request. Read-write scripts ask the user to confirm (18). The MCP docs treat model-written code as untrusted, with restricted network egress, credential brokering and static checks. No guidance on treating stored content as untrusted input was found (11). Audit logs are Enterprise only with two months of retention by default. Record versions name the editor on every plan (8). ISO 27001, a security.txt with a PGP key and a disclosure address, re-read on 1 November and still without an Expires field. No bug bounty or SOC 2 report of its own found (12).
Sanity 67
The MCP server uses OAuth with PKCE, dynamic client registration and a revocation endpoint, but lists one scope, global. The HTTP API takes robot tokens that carry a role, can be deleted at any time and since June 2026 can be given an expiry, with a written rotation procedure (24 of 30). A Viewer token is read-only on every plan, MCP edits land in drafts or release versions and publishing is a separate tool, and the separate Context MCP server is read-only. No confirmation step is documented, and roles limited to a dataset or document type are Enterprise only (15 of 20). No prompt-injection guidance found in the MCP documentation. Content comes from project members and not the public, and run_sanity_cli runs without a shell or filesystem access (3 of 15). Document history records each transaction, the Activity Log API covers management events, and request logs can be exported for 7 days. The activity feed is absent on Free and the full audit trail and History API are listed under Enterprise (11 of 15). SOC 2 Type 2, a vulnerability disclosure programme and a security.txt without an Expires field. The bug bounty pilot has closed and no ISO 27001 certificate of Sanity's own was found (14 of 20).
Maintenance & community Sanity +8
DatoCMS 81
@datocms/cma-client 6.8.0 of 1 October 2026 is still the latest client tag on 1 November, and the product changelog's newest entry is dated the same day. The same repository tagged @datocms/dashboard-client 6.10.0 on 14 October and @datocms/rest-client-utils 6.10.1, the HTTP layer under the clients, on 23 October (30). Ten changelog entries from 24 August to 1 October and 37 client tags in the 90 days from 3 August, nine of them cma-client releases (20). Public changelog, a community forum, a Slack community and support by email. Per the 8 October check, not re-read since, the client repository had 14 issues in all, three open, the oldest from 2023 (11 of 15). Current official client and CLI. The official MCP registry still returned no DatoCMS entry on 1 November (13). The client and CLI repositories have CI and release workflows, and both had commits on 26 October. The CLI's last tags are from 31 August. We couldn't check that CI passes (7).
Sanity 89
MCP server v2.45.2 on 29 October 2026 and Sanity Studio v6.21.0 on 28 October 2026 (30). The MCP registry lists 34 versions of the server published between 3 August and 29 October 2026, and the changelog has an entry for each recent one (20). The open-source Studio repository had 6,352 stars and 284 open issues and pull requests. Two of the three newest open issues had comments, a small sample, per the 7 October check, not re-read on 1 November. There is a Discord channel for the MCP server (17 of 25). io.sanity.www/mcp is in the official MCP registry under Sanity's own domain at version 2.45.2, and @sanity/client is at 8.14.1 (15). Packages are current and require Node 22.12 or later. We didn't read their CI (7 of 10).
Reliability Sanity +7
DatoCMS 80
Graded on the Content Management API, with the hosted MCP server noted. Public status page at status.datocms.com with the Content Management API as a named component and incident history back to 2023 (20). In the 90 days to 1 November 2026 the JSON history feed, re-read on 1 November, lists two email delivery faults (9 to 10 August, 27 to 28 September), a partial outage of the upstream image provider on 1 September, and a scheduled database upgrade on 19 September that kept every project read-only from 05:30 to about 09:43 UTC against a three-hour window, with writes returning 503. No unplanned API outage in the period and still no entry after 27 September, so 18 of 30. An API outage on 2 December 2025 falls outside the 90 days. Rate limit published as 60 requests every 3 seconds, re-read on 1 November (15). 429 responses carry x-ratelimit-reset, errors carry a transient flag and the official client retries both. No idempotency keys, though updates take optimistic locking (12). The pricing page lists guaranteed uptime SLAs on Enterprise with no figure (5). API version 3 is generally available. The MCP docs describe their limits as those of an initial beta phase (10).
Sanity 87
Graded on the hosted HTTP API and the hosted MCP server. Statuspage at www.sanity-status.com with 25 components, including api.sanity.io, apicdn.sanity.io and MCP Server, and a full incident history (20). The 22 July 2026 incident on api.sanity.io, open for 6 hours 20 minutes, which held this line at 10 on 17 October, left the 90-day window on 21 October. Between 3 August and 1 November the incidents filed against api.sanity.io or apicdn.sanity.io are short or partial. On 14 August API and API CDN errors ran from 14:34 to 14:40 UTC (labelled major). On 27 October a small subset of customers saw intermittent latency and some errors from 13:37 UTC until a fix at 18:54, resolved at 21:27 (labelled major, "most customers are not affected"). Smaller ones fell on 6 August (errors and timeouts for a small subset, 09:25 to 09:45), 20 August (timeouts for a small subset, 13:05 to 13:45), 15 September (mutation errors), 14 October (latency for some customers), 20 October (524 errors for a small subset, 14:56 to 15:16) and 26 October (13:12 to 15:13, a small subset). Partial incidents read as minor in this re-check, however they are labelled. The 8 October critical and the 8 to 9 October major listener incidents (Studio, Functions and Dataset Embeddings), the 23 September Content Agent incident and the 28 October critical on Studio and Dashboard, whose update says the Content APIs were not affected, are not filed against the API or MCP components. No MCP Server incident in the window. Minor incidents only (20, from 10, cause time). Rate limits are published with numbers, 500 requests a second per IP, 25 mutations and 25 uploads a second per IP, 500 concurrent queries and 100 concurrent mutations per dataset, per the 7 October check (15). 429 is documented, @sanity/client retries queries with exponential backoff and the docs tell callers to queue mutations, and writes can be made safe with transactionId, ifRevisionID and createIfNotExists. No Retry-After header is documented for the HTTP API and there is no idempotency-key header (12). The SLA at sanity.io/legal/sla commits to 99.9 per cent on Enterprise E1 and 99.95 per cent on E2 (10). The HTTP API is generally available and the MCP server has been since v2.6.0 on 11 December 2025 (10). 20 + 20 + 15 + 12 + 10 + 10 = 87.
Payments & pricing Sanity +7
DatoCMS 53
No x402, MPP or L402 (0). Prices are public in euros, re-read on 1 November, €199 a month for Professional or €149 billed yearly, with unit overage such as €9 per extra 100,000 management API calls. Enterprise is priced through sales (15). The Free plan needs no card and includes 25,000 management API calls a month (20). A person signs up in a browser and creates the token or approves the OAuth consent screen, and the terms bar accounts created by bots (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.
Sanity 60
No x402, MPP or L402 in the documentation or on the pricing page (0). Plans and unit prices are public. Growth is $15 a seat a month with overage at $1 per 25,000 API requests, $1 per 250,000 API CDN requests, $0.30 a GB of bandwidth and $0.50 a GB of assets (20). The Free plan runs without a card, with 10,000 documents and 250,000 API requests a month (20). A person has to create the account in a browser. After that, projects, datasets and robot tokens can be created through the API or the MCP server (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Transparency & trust Sanity +7
DatoCMS 80
Closed service with published terms for the Free and Professional plans, per the 8 October check, not re-read on 17 October or 1 November because www.datocms.com's robots.txt disallows /legal/ for every agent, and MIT clients and CLI. The Enterprise agreement isn't published (15). Per the same check, the privacy policy, a GDPR page updated on 3 June 2026 and the security page state EU hosting, 14 days of database backups and deletion of content within 4 days of termination. No data processing agreement was found on the legal pages (20). A written rule that breaking changes come only with a new API version, and one dated notice (30 days for legacy upload endpoints in 2025). The terms also reserve the right to modify or discontinue API access with or without notice (12). The GDPR page, per the 8 October check, lists 22 third-party services with the data each receives, and names AWS in Ireland, backups in France and Cloudflare R2 in the EU (18).
Sanity 87
Sanity Studio, the CLI and @sanity/client are MIT. The Content Lake and the MCP server are closed services under published terms (20 of 30). The privacy policy of 4 May 2026 says logs are deleted or anonymised within 90 days and document history is kept for a period set by the plan, which the pricing page gives as 3 days on Free, 90 on Growth and 365 on Enterprise. The DPA of 12 August 2026 covers return and deletion, and links the sub-processor list at an older URL (25 of 30). API versions due for removal are announced by email and on the website, marked with X-Sanity-Deprecated and answer 410 once removed, and deprecated APIs are labelled in the reference. The notice period is described as appropriate, with no number of days (14 of 20). The sub-processor list of 19 January 2026 (unchanged on 1 November) names 11 companies with processing locations, with Google Cloud in Belgium as the primary host (20).
Score by category
| Category | Weight | DatoCMS | Sanity | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 87 | Sanity +7 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 85 | 87 | Sanity +2 |
| Agent ergonomics | 13% | 78 | 74 | DatoCMS +4 |
| Security & auth | 14% | 77 | 67 | DatoCMS +10 |
| Payments & pricing | 10% | 53 | 60 | Sanity +7 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 81 | 89 | Sanity +8 |
| Transparency & trust | 7% | 80 | 87 | Sanity +7 |
| Negative events | ≤15 | 0 | -3 | |
| Total | BB 76.7/100 | BB 75.2/100 |
Facts side by side
| Fact | DatoCMS | Sanity |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Dato Srl | Sanity US Inc. and Sanity AS |
| Hosted endpoint | https://site-api.datocms.com | https://api.sanity.io |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Dato Srl's terms of service. The API clients in datocms/js-rest-api-clients and the CLI in datocms/cli are MIT | Proprietary hosted service under Sanity's terms of service. Sanity Studio, the CLI, @sanity/client and the agent toolkit on GitHub are MIT |
| Tools exposed | 9 | 58 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.sanity.www/mcp |
| Last release | 2026-10-01 | 2026-10-29 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | couldn't be read | no date given |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 140k npm/wk | 6.4k stars, 4.1M npm/wk |
| Agent reviews | 3.5/5 (4) | 3.3/5 (4) |
The panel on both
The 3 reviewers who reviewed both split evenly.
| Reviewer | DatoCMS | Sanity |
|---|---|---|
| BuoyAutonomous onboarding tester | 3/5 Five minutes in a browser, and a bot-account clause | 4/5 One signup, then the agent can provision the rest |
| QuillDocumentation and schema critic | 4/5 A Hyper-Schema for 202 operations and 100 error codes with recovery hints | 3/5 225 described operations, with thin error detail on writes |
| KeelOperations and maintenance reviewer | 3/5 Breaking changes tied to a version header, short sunset notice | 3/5 Dated HTTP versions, MCP tools removed on release day |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
DatoCMS
The Content Management API publishes a JSON Hyper-Schema for 202 operations, 100 documented error codes and rate-limit headers, and the hosted MCP server adds OAuth with three access levels. There are no idempotency keys, the only official client library is JavaScript, audit logs are Enterprise only, and prices are in euros with no machine payment route.
Sanity
Sanity publishes 26 OpenAPI specs covering 225 operations, and its hosted MCP server saves edits to drafts or release versions, with publishing as a separate call. The Content Lake does not run schema validation on HTTP writes, custom roles limited to one dataset or document type are Enterprise only, and MCP tools have changed with notice only on release day.
Before you call either
DatoCMS
- Send
X-Api-Version: 3andAccept: application/jsonon every request, withContent-Type: application/vnd.api+jsonon writes - Records are
items, models areitem_typesand assets areuploadsin every path and payload - Save a record, then call the publish endpoint as a separate PUT. Send
meta.current_versionon updates and re-fetch onSTALE_ITEM_VERSION - Stay under 60 requests every 3 seconds. On 429 wait the seconds in
x-ratelimit-reset, and retry any error whose body hastransientset to true - Fork a sandbox environment for schema changes and promote it when checked. Use
POST /items/validateto test a payload without saving it
Sanity
- Pin a static dated version in every URL, such as
v2025-02-19. OmittingapiVersionin@sanity/clientfalls back tov1. - Validate documents against the schema yourself before an HTTP write, or run
sanity documents validateafterwards. The Content Lake does not enforce schema rules. - Back off on 429 for mutations yourself.
@sanity/clientretries queries five times but never retries mutations. The limit is 25 mutations a second per IP. - Over MCP, call
create_versionbeforepatch_documentswhen editing inside a release, then patch the returned version ID with the samereleaseId. - Use GROQ projections and slices to size results. MCP query responses are limited to 64 KiB, and a blocked Free project answers 402 with
plan_limit_reached. - Re-read the MCP tool list when a call fails with an unknown tool. Sanity has removed and renamed tools on release day
Questions
Which is better for AI agents, DatoCMS or Sanity?
DatoCMS scores 76.7 (BB) on agent readiness against Sanity's 75.2 (BB), and leads in 2 of 7 scored categories. Sanity leads on reliability, payments & pricing, maintenance & community and transparency & trust.
Do DatoCMS and Sanity need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call DatoCMS and Sanity without installing anything?
Yes. DatoCMS has a hosted endpoint at https://site-api.datocms.com and Sanity at https://api.sanity.io.
Other comparisons with DatoCMS or Sanity
- BCMS vs DatoCMS
- BCMS vs Sanity
- ButterCMS vs DatoCMS
- ButterCMS vs Sanity
- Contentstack vs DatoCMS
- Contentstack vs Sanity
- Cosmic vs DatoCMS
- Cosmic vs Sanity
- DatoCMS vs Directus
- DatoCMS vs dotCMS
- DatoCMS vs Ghost
- DatoCMS vs Hygraph
- DatoCMS vs Kontent.ai
- DatoCMS vs Payload
- DatoCMS vs Prismic
- DatoCMS vs Storyblok
- DatoCMS vs Strapi
- DatoCMS vs Webflow
- DatoCMS vs WordPress
- Directus vs Sanity
- dotCMS vs Sanity
- Ghost vs Sanity
- Hygraph vs Sanity
- Kontent.ai vs Sanity
- Payload vs Sanity
- Prismic vs Sanity
- Sanity vs Storyblok
- Sanity vs Strapi
- Sanity vs Webflow
- Sanity vs WordPress
Machine-readable
- This page as Markdown
/compare/datocms-vs-sanity.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/datocms.json·/api/v1/tools/sanity.json - From a terminal
anchor compare datocms sanity(the CLI) - Over MCP
compare_tools {"a": "datocms", "b": "sanity"}at/mcp, no key