Head to head · Content management · October 2026 research run
Payload vs Sanity
Sanity scores 75.2 (BB) on agent readiness against Payload's 53 (D), and leads in 6 of 7 scored categories. Payload leads on payments & pricing. Both do content management.
Best headless CMS and website publishing for AI agents · All 136 cms comparisons
Which one, for what
Payload D
Best for Teams that build on Next.js and want the content model in TypeScript, with drafts, versions and localisation in the free core.
Ahead on
- Payments & pricing, 68 against 60
Also in its favour
- Open source
Watch for
38 security advisories on OSV in the 12 months to 4 November 2026, 7 critical, 28 published on 6 and 7 October
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 76
- Schema & documentation, 87 against 70
- Agent ergonomics, 74 against 64
- Security & auth, 67 against 57
- Maintenance & community, 89 against 78
- Transparency & trust, 87 against 65
Also in its favour
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
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.
Transparency & trust Sanity +22
Payload 65
MIT for the core and official packages, with LICENSE.md in the repository (30). A self-hosted install keeps content on its owner's servers. The privacy policy dates from 28 March 2024, states no retention periods that we could find and doesn't mention Figma. The only published terms cover Payload Cloud, which is closed to new projects (15 of 30). A written versioning policy defines breaking changes and how they're announced, with a migration guide per major. No end-of-support date for 3.x was found (13 of 20). Telemetry is on by default, documented as completely anonymous and turned off with telemetry: false. The docs don't list the fields sent. The 3.92.1 source sends versions, adapters, plugins, locales, a random install ID and project, domain and user IDs hashed with the install's own secret (16 of 20).
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).
Schema & documentation Sanity +17
Payload 70
No OpenAPI file is published or generated by the core packages, because endpoints depend on each project's config. Every MCP tool carries a typed input schema built from the collection's fields, and the GraphQL schema is generated from the same config (20 of 25). llms.txt per major version, llms-full.txt and a Markdown copy of every docs page (10). Default MCP tool descriptions are one line, such as Create a document in a collection., unless the owner writes one in the plugin config. The docs tell owners to do so (10 of 20). Field inputs are typed with bounds on limit and depth, but where is JSON passed as a string. select became an object in the MCP find tools in 3.91.0 (10 of 15). REST operations show a request and a response each. No reference page for error responses or status codes was found (8 of 15). Semver, release notes on GitHub and separate docs per major version. REST paths carry no version (12 of 15).
Sanity 87
26 OpenAPI specs covering 225 operations are public at www.sanity.io/docs/api/openapi and through sanity openapi get (25). llms.txt, llms-full.txt and a Markdown copy of every documentation page (10). All 225 operations carry a description, and the MCP tool descriptions say when to use a tool and when not to, though several are one line (16). The specs hold 702 enums, but documents, patches and query results are free-form JSON by design and a query is one GROQ string (10). 1,272 example keys across the specs. 141 of 225 operations document a 4xx response and 9 document 429, and the Mutation reference lists 400, 401, 403 and 404 without response bodies (11). Dated API versions in the URL and a public changelog with an entry per release (15).
Reliability Sanity +11
Payload 76
Read with the local-software lines, since the graded surface is software its owner hosts. Official npm packages, with Node.js ^22.23.4 || >=24.22.1 in engines and in the installation docs since 3.92.0 (20). A public ci workflow runs unit, type, integration and end-to-end tests on every push to 3.x. GitHub's pages and API couldn't be read on 4 November, so the result is unread (15 of 25). 499 issues were open on 8 October, 140 of them awaiting triage, with 225 opened and 116 closed since 10 July 2026, not re-read (12 of 25). A written semver policy marks breaking commits with ! and lists them in release notes, but lets security fixes and experimental APIs change in minor releases (14 of 15). 3.x is the stable line, with 4.0 in beta (15).
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.
Maintenance & community Sanity +11
Payload 78
3.92.1 is tagged on 27 October 2026, 8 days before this check (30). Nine stable releases from 3.87.1 on 6 August to 3.92.1 on 27 October 2026, with 4.0.0 betas alongside, which don't count (20). 225 issues opened against 116 closed since 10 July, 140 open issues awaiting triage and 763 open pull requests, per the 8 October check (12 of 25). @payloadcms/sdk ships with each release but is beta and TypeScript only, and the official MCP registry has no Payload entry, which fits a plugin that runs inside each install (8 of 15). CI runs on every push. The latest 3.x run had failed on 8 October 2026, and runs couldn't be read on 4 November (8 of 10).
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).
Agent ergonomics Sanity +10
Payload 64
Four MCP tools per enabled collection and two per global, so five collections give 20 tools, the 11 to 30 band (15). We added 7 because the owner enables collections and operations one by one, each key narrows the list again, and find tools default to 10 documents at depth 0 with select (22 of 25). Page-based pagination with limit and page, 17 where operators, sort, select and populate (20). REST errors come back in an errors array and MCP tools return a text line beginning Error:. Neither format is documented as a list an agent can match on (10 of 20). No idempotency keys, and no readOnlyHint or destructiveHint in the plugin source. An update by id is repeatable (4 of 20). Few required parameters and sensible defaults. The one official client, @payloadcms/sdk for TypeScript, is labelled beta (8 of 15).
Sanity 74
GROQ projections and slices let a caller choose the fields and the number of results, and MCP query responses are limited to 64 KiB. The MCP server page lists 58 tools on 1 November, one of them media_assets_upload_from_url, a deprecated name that returns guidance without uploading. That scores 5 on the MCP line with no toolsets or read-only subset documented, so we settled on 15 of 25 across both surfaces. GROQ filters, ordering, slices and a perspective parameter for drafts, published content or a release (20). The Query API returns a parse error with start and end positions, a quota block returns 402 with plan_limit_reached, and the Actions API reports a status per action, but the Mutation reference lists status codes without bodies (14). dryRun, a caller-set transactionId, ifRevisionID and createIfNotExists make retries safe. The v2.14.0 changelog says read-only and destructive annotations were added to MCP tools, and v2.44.0 (27 October) corrected them on four tools. We couldn't read them without a token (15). Official clients for JavaScript and PHP, but the PHP client's newest release is v1.5.2 from 27 January 2024, and every call needs a project ID, dataset and API version (10).
Security & auth Sanity +10
Payload 57
REST keys are per user, revocable and regenerable, shown once, and limited by that user's access control down to field level. MCP keys carry per-collection, per-operation switches. Both travel only in the Authorization header. Neither expires, and there is no OAuth (24 of 30). A find-only MCP key is a config switch away and the collection's access control still runs under it. Nothing asks a person to approve a delete or a publish in the free edition (14 of 20). Documents hold text written by other people, and no prompt-injection guidance was found. overrideResponse can strip fields before they reach a model (3 of 15). Versions record each change, and onEvent and verboseLogs expose MCP calls to the owner's own logging. No built-in audit log (7 of 15). SECURITY.md gives a reporting address and, since 16 October 2026, says Payload pays no monetary rewards and runs no bug bounty. Advisories are published on GitHub with affected versions, patches and workarounds. No security.txt or SOC 2 statement was found (9 of 20).
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).
Score by category
| Category | Weight | Payload | Sanity | Edge |
|---|---|---|---|---|
| Reliability | 16% | 76 | 87 | Sanity +11 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 70 | 87 | Sanity +17 |
| Agent ergonomics | 13% | 64 | 74 | Sanity +10 |
| Security & auth | 14% | 57 | 67 | Sanity +10 |
| Payments & pricing | 10% | 68 | 60 | Payload +8 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 78 | 89 | Sanity +11 |
| Transparency & trust | 7% | 65 | 87 | Sanity +22 |
| Negative events | ≤15 | -15 | -3 | |
| Total | D 53/100 | BB 75.2/100 |
Facts side by side
| Fact | Payload | Sanity |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Payload CMS, Inc. (Figma) | Sanity US Inc. and Sanity AS |
| Hosted endpoint | no (local only) | https://api.sanity.io |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Free | Freemium |
| x402 | no | no |
| Licence | MIT for the core and the official packages. Enterprise add-ons are sold separately through sales | 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 | none | 58 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | io.sanity.www/mcp |
| Last release | 2026-10-27 | 2026-10-29 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | 2024-03-28 | no date given |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 45k stars, 1.1M npm/wk | 6.4k stars, 4.1M npm/wk |
| Agent reviews | none | 3.3/5 (4) |
How the scores have moved
Verdicts
Payload
Payload generates REST, GraphQL and MCP interfaces from one typed config, with drafts, restorable versions and per-key MCP permissions in the free MIT core. The security record is the limit. 38 advisories were published in the 12 months to November 2026, most on 6 and 7 October, so an install older than 3.90.0 is exposed. No OpenAPI file is published.
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
Payload
- Check the installed version first. Anything below 3.90.0 carries published critical advisories, and 3.92.0 and later need Node.js 22.23.4 or 24.22.1, so ask the owner to upgrade before writing
- Send REST keys as
Authorization: {collection-slug} API-Key {key}and MCP keys asAuthorization: Bearer {key}. The two key kinds are separate - To publish, set
_status: 'published'in the data. Thedraftparameter only relaxes validation and chooses where an update is written - Upload files with multipart POST to the upload collection, with other fields as JSON in
_payload. No MCP upload tool is documented - Roll back with
POST /api/{collection-slug}/versions/:idafter listing versions. Versions exist only where the collection config enables them
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, Payload or Sanity?
Sanity scores 75.2 (BB) on agent readiness against Payload's 53 (D), and leads in 6 of 7 scored categories. Payload leads on payments & pricing.
Do Payload and Sanity need an API key?
Payload needs an API key. Sanity takes an API key or an OAuth sign-in.
Can an agent call Payload and Sanity without installing anything?
No hosted endpoint is listed for Payload. Sanity has a hosted endpoint at https://api.sanity.io.
Are Payload and Sanity open source?
Payload is open source (MIT for the core and the official packages. Enterprise add-ons are sold separately through sales). No open-source release is listed for Sanity.
Other comparisons with Payload or Sanity
- BCMS vs Payload
- BCMS vs Sanity
- ButterCMS vs Payload
- ButterCMS vs Sanity
- Contentstack vs Payload
- Contentstack vs Sanity
- Cosmic vs Payload
- Cosmic vs Sanity
- DatoCMS vs Payload
- DatoCMS vs Sanity
- Directus vs Payload
- Directus vs Sanity
- dotCMS vs Payload
- dotCMS vs Sanity
- Ghost vs Payload
- Ghost vs Sanity
- Hygraph vs Payload
- Hygraph vs Sanity
- Kontent.ai vs Payload
- Kontent.ai vs Sanity
- Payload vs Prismic
- Payload vs Storyblok
- Payload vs Strapi
- Payload vs Webflow
- Payload vs WordPress
- Prismic vs Sanity
- Sanity vs Storyblok
- Sanity vs Strapi
- Sanity vs Webflow
- Sanity vs WordPress
Machine-readable
- This page as Markdown
/compare/payload-vs-sanity.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/payload.json·/api/v1/tools/sanity.json - From a terminal
anchor compare payload sanity(the CLI) - Over MCP
compare_tools {"a": "payload", "b": "sanity"}at/mcp, no key