Head to head · Cms content · October 2026 research run
Sanity vs Storyblok
Sanity scores 73.7 (BB) on agent readiness against Storyblok's 67.7 (B), and leads in 4 of 7 scored categories. Storyblok leads on security & auth. Both do cms content.
Which one, for what
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
- Schema & documentation, 87 against 68
- Payments & pricing, 40 against 35
- Maintenance & community, 89 against 80
- Transparency & trust, 87 against 80
Also in its favour
- Agent-ready, a grade of BB or better
- No incidents deducted, where Storyblok loses 3 points for them
Watch for
Schema validation rules run only in Sanity Studio. The HTTP mutation API accepts a document without checking them
Good for Teams already on Storyblok who want an agent to draft, translate and publish stories or change component schemas under scoped, per-space permissions.
Ahead on
- Security & auth, 73 against 67
Also in its favour
- Free to start without a card
Watch for
The Management API's OpenAPI spec sits in a private repository. Only the Content Delivery API has a public spec (OpenAPI 3.1, 14 operations)
Score by category
| Category | Weight this run | Sanity | Storyblok | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 77 | 79 | Storyblok +2 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 87 | 68 | Sanity +19 |
| Agent ergonomics | 13%16.2 | 74 | 78 | Storyblok +4 |
| Security & auth | 14%17.5 | 67 | 73 | Storyblok +6 |
| Payments & pricing | 10%12.5 | 40 | 35 | Sanity +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 89 | 80 | Sanity +9 |
| Transparency & trust | 7%8.8 | 87 | 80 | Sanity +7 |
| Negative events | ≤15 | 0 | -3 | |
| Total | 73.7 · BB | 67.7 · B |
Facts side by side
| Fact | Sanity | Storyblok |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Sanity US Inc. and Sanity AS | Storyblok GmbH |
| Hosted endpoint | https://api.sanity.io | https://mapi.storyblok.com/v1 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Proprietary hosted service under Sanity's terms of service. Sanity Studio, the CLI, @sanity/client and the agent toolkit on GitHub are MIT | Proprietary service under Storyblok's terms. The SDKs, API clients and CLI in storyblok/monoblok are MIT |
| Tools exposed | 53 | 7 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | io.sanity.www/mcp | not listed |
| Last release | 2026-10-02 | 2026-10-02 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | no date given | 2025-10-06 |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 6.4k stars, 4.1M npm/wk | 68 stars, 433k npm/wk |
Verdicts
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.
Storyblok
The hosted MCP server covers the whole Management API with seven tools, OAuth scopes split into read, write and publish per space, and a confirmation step on deletes. The Management API has no public OpenAPI spec, no idempotency keys and no monitor on the public status page, and publishing is a GET request.
Before you call either
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.
Storyblok
- Pick the base URL by the space's region (mapi.storyblok.com for the EU, api-us, api-ca or api-ap otherwise). A token sent to the wrong region fails
- Create stories without
publishto keep them as drafts, then call the publish endpoint. It is a GET, so never prefetch or blindly retry it - Write translations as
field__i18n__<code>keys inside the same content object, and set the component field to translatable first - Upload an asset in three steps (signed response, POST to S3, finish upload). Through MCP the S3 step needs shell access for curl
- Stay under 3 calls a second on Starter and 6 on paid plans, and back off exponentially on 429. Saves that break a field's max_length return 422
Questions
Which is better for AI agents, Sanity or Storyblok?
Sanity scores 73.7 (BB) on agent readiness against Storyblok's 67.7 (B), and leads in 4 of 7 scored categories. Storyblok leads on security & auth.
Do Sanity and Storyblok need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Sanity and Storyblok without installing anything?
Yes. Sanity has a hosted endpoint at https://api.sanity.io and Storyblok at https://mapi.storyblok.com/v1.
Other comparisons with Sanity or Storyblok
Machine-readable
- This page as Markdown
/compare/sanity-vs-storyblok.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/sanity.json·/api/v1/tools/storyblok.json - From a terminal
anchor compare sanity storyblok(the CLI) - Over MCP
compare_tools {"a": "sanity", "b": "storyblok"}at/mcp, no key