# DatoCMS vs Sanity

> DatoCMS and Sanity score within a point of each other on agent readiness, 74.4 (BB) and 73.7 (BB). Sanity leads on payments & pricing, maintenance & community and transparency & trust. Both do cms content. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/datocms-vs-sanity
- Markdown: https://www.anchorterminal.com/compare/datocms-vs-sanity.md (~2,250 tokens)
- Slim: https://www.anchorterminal.com/compare/datocms-vs-sanity.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/datocms-vs-sanity.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-08

DatoCMS and Sanity score within a point of each other on agent readiness, 74.4 (BB) and 73.7 (BB). Sanity leads on payments & pricing, maintenance & community and transparency & trust. Both do cms content.

- DatoCMS: grade BB, 74.4/100, rank #62 of 722. Markdown https://www.anchorterminal.com/tools/datocms.md · JSON https://www.anchorterminal.com/api/v1/tools/datocms.json
- Sanity: grade BB, 73.7/100, rank #73 of 722. Markdown https://www.anchorterminal.com/tools/sanity.md · JSON https://www.anchorterminal.com/api/v1/tools/sanity.json

## Which one, for what

### DatoCMS (BB)

Good 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

Watch for: No idempotency keys in the reviewed documentation. Safe retries rest on optimistic locking and the JavaScript client's automatic retry

### Sanity (BB)

Good 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:
- Payments & pricing, 40 against 35
- Maintenance & community, 89 against 81
- Transparency & trust, 87 against 80

Watch for: Schema validation rules run only in Sanity Studio. The HTTP mutation API accepts a document without checking them


## Score by category

| Category | Weight | DatoCMS | Sanity | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 80 | 77 | DatoCMS +3 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 85 | 87 | Sanity +2 |
| Agent ergonomics | 13% (16.2 this run) | 78 | 74 | DatoCMS +4 |
| Security & auth | 14% (17.5 this run) | 77 | 67 | DatoCMS +10 |
| Payments & pricing | 10% (12.5 this run) | 35 | 40 | Sanity +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 81 | 89 | Sanity +8 |
| Transparency & trust | 7% (8.8 this run) | 80 | 87 | Sanity +7 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **74.4 · BB** | **73.7 · BB** | |

## 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 | 53 |
| 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-02 |
| 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 | 153k npm/wk | 6.4k stars, 4.1M npm/wk |

## 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 API writes, and custom roles that limit a token to one dataset or document type are sold only on Enterprise plans.

## Before you call either

### DatoCMS

1. Send `X-Api-Version: 3` and `Accept: application/json` on every request, with `Content-Type: application/vnd.api+json` on writes
2. Records are `items`, models are `item_types` and assets are `uploads` in every path and payload
3. Save a record, then call the publish endpoint as a separate PUT. Send `meta.current_version` on updates and re-fetch on `STALE_ITEM_VERSION`
4. Stay under 60 requests every 3 seconds. On 429 wait the seconds in `x-ratelimit-reset`, and retry any error whose body has `transient` set to true
5. Fork a sandbox environment for schema changes and promote it when checked. Use `POST /items/validate` to test a payload without saving it

### Sanity

1. Pin a static dated version in every URL, such as `v2025-02-19`. Omitting `apiVersion` in `@sanity/client` falls back to `v1`.
2. Validate documents against the schema yourself before an HTTP write, or run `sanity documents validate` afterwards. The Content Lake does not enforce schema rules.
3. Back off on 429 for mutations yourself. `@sanity/client` retries queries five times but never retries mutations. The limit is 25 mutations a second per IP.
4. Over MCP, call `create_version` before `patch_documents` when editing inside a release, then patch the returned version ID with the same `releaseId`.
5. 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`.

## Questions

### Which is better for AI agents, DatoCMS or Sanity?

DatoCMS and Sanity score within a point of each other on agent readiness, 74.4 (BB) and 73.7 (BB). Sanity leads on 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.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/datocms-vs-sanity.json, and with the fewest tokens: https://www.anchorterminal.com/compare/datocms-vs-sanity.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "datocms", "b": "sanity"}`. From a terminal: `anchor compare datocms sanity`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/datocms.json and https://www.anchorterminal.com/api/v1/tools/sanity.json

## Other comparisons with DatoCMS or Sanity

- [Contentstack vs DatoCMS](https://www.anchorterminal.com/compare/contentstack-vs-datocms.md)
- [Contentstack vs Sanity](https://www.anchorterminal.com/compare/contentstack-vs-sanity.md)
- [DatoCMS vs Directus](https://www.anchorterminal.com/compare/datocms-vs-directus.md)
- [DatoCMS vs Ghost](https://www.anchorterminal.com/compare/datocms-vs-ghost.md)
- [DatoCMS vs Payload](https://www.anchorterminal.com/compare/datocms-vs-payload.md)
- [DatoCMS vs Storyblok](https://www.anchorterminal.com/compare/datocms-vs-storyblok.md)
- [DatoCMS vs Strapi](https://www.anchorterminal.com/compare/datocms-vs-strapi.md)
- [DatoCMS vs Webflow](https://www.anchorterminal.com/compare/datocms-vs-webflow.md)
- [DatoCMS vs WordPress](https://www.anchorterminal.com/compare/datocms-vs-wordpress.md)
- [Directus vs Sanity](https://www.anchorterminal.com/compare/directus-vs-sanity.md)
- [Ghost vs Sanity](https://www.anchorterminal.com/compare/ghost-vs-sanity.md)
- [Payload vs Sanity](https://www.anchorterminal.com/compare/payload-vs-sanity.md)
- [Sanity vs Storyblok](https://www.anchorterminal.com/compare/sanity-vs-storyblok.md)
- [Sanity vs Strapi](https://www.anchorterminal.com/compare/sanity-vs-strapi.md)
- [Sanity vs Webflow](https://www.anchorterminal.com/compare/sanity-vs-webflow.md)
- [Sanity vs WordPress](https://www.anchorterminal.com/compare/sanity-vs-wordpress.md)