Head to head · Cms content · October 2026 research run
Sanity vs WordPress
Sanity scores 73.7 (BB) on agent readiness against WordPress's 64.8 (B), and leads in 4 of 7 scored categories. WordPress leads on payments & pricing. 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 65
- Security & auth, 67 against 62
- Maintenance & community, 89 against 83
- Transparency & trust, 87 against 68
Also in its favour
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- No incidents deducted, where WordPress loses 5 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 Sites that already run WordPress, where an agent drafts posts and uploads media under a Contributor or Author account and a person publishes.
Ahead on
- Payments & pricing, 60 against 40
Also in its favour
- Runs on your own machine
- Open source
Watch for
Application Passwords have no scopes or expiry. Each one carries every capability of its user
Score by category
| Category | Weight this run | Sanity | WordPress | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 77 | 78 | WordPress +1 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 87 | 65 | Sanity +22 |
| Agent ergonomics | 13%16.2 | 74 | 74 | even |
| Security & auth | 14%17.5 | 67 | 62 | Sanity +5 |
| Payments & pricing | 10%12.5 | 40 | 60 | WordPress +20 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 89 | 83 | Sanity +6 |
| Transparency & trust | 7%8.8 | 87 | 68 | Sanity +19 |
| Negative events | ≤15 | 0 | -5 | |
| Total | 73.7 · BB | 64.8 · B |
Facts side by side
| Fact | Sanity | WordPress |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Sanity US Inc. and Sanity AS | WordPress.org (open-source project) |
| Hosted endpoint | https://api.sanity.io | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Free |
| 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 | GPL-2.0-or-later. The MCP Adapter plugin is GPL-2.0-or-later too |
| Tools exposed | 53 | none |
| 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-06 |
| Terms last updated | no date given | no document linked |
| Privacy policy last updated | no date given | no date given |
| Customer content may train models | not found in the text | |
| Terms restrict automated access | not found in the text | |
| Terms restrict benchmarking | yes | |
| Terms or service can change without notice | not found in the text | |
| Arbitration or class-action waiver | not found in the text | |
| Popularity | 6.4k stars, 4.1M npm/wk | 21k stars |
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.
WordPress
The REST API is part of core, and a post created without a status is saved as a draft with revisions kept on the owner's server. Application Passwords carry no scopes, so limits come only from the user's role. Revisions can be read and deleted but not restored over REST, and a critical flaw was fixed on 22 September 2026.
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.
WordPress
- Ask the owner for a dedicated user with the lowest role that fits. A Contributor can draft and edit its own posts but can't publish them
- Send the Application Password as Basic auth over HTTPS only. Core disables Application Passwords on plain HTTP outside a local environment
- Upload a file with POST
/wp-json/wp/v2/mediafirst, then setfeatured_mediaor reference the returned URL in the post content - To roll back, GET
/wp/v2/posts/<id>/revisions/<rev>?context=editand POST its title and content to the post. There's no restore route - Pass
_fields=id,status,link,modifiedon lists and read X-WP-TotalPages.per_pagestops at 100
Questions
Which is better for AI agents, Sanity or WordPress?
Sanity scores 73.7 (BB) on agent readiness against WordPress's 64.8 (B), and leads in 4 of 7 scored categories. WordPress leads on payments & pricing.
Do Sanity and WordPress need an API key?
Sanity takes an API key or an OAuth sign-in. WordPress needs an API key.
Can an agent call Sanity and WordPress without installing anything?
Sanity has a hosted endpoint at https://api.sanity.io. WordPress runs on your own machine, with no hosted endpoint listed.
Are Sanity and WordPress open source?
No open-source release is listed for Sanity. WordPress is open source (GPL-2.0-or-later. The MCP Adapter plugin is GPL-2.0-or-later too).
Other comparisons with Sanity or WordPress
Machine-readable
- This page as Markdown
/compare/sanity-vs-wordpress.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/sanity.json·/api/v1/tools/wordpress.json - From a terminal
anchor compare sanity wordpress(the CLI) - Over MCP
compare_tools {"a": "sanity", "b": "wordpress"}at/mcp, no key