# DatoCMS vs WordPress

> DatoCMS scores 74.4 (BB) on agent readiness against WordPress's 64.8 (B), and leads in 5 of 7 scored categories. WordPress leads on payments & pricing. Both do cms content. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/datocms-vs-wordpress
- Markdown: https://www.anchorterminal.com/compare/datocms-vs-wordpress.md (~2,300 tokens)
- Slim: https://www.anchorterminal.com/compare/datocms-vs-wordpress.min.md (~780 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/datocms-vs-wordpress.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 scores 74.4 (BB) on agent readiness against WordPress's 64.8 (B), and leads in 5 of 7 scored categories. WordPress leads on payments & pricing. 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
- WordPress: grade B, 64.8/100, rank #272 of 722. Markdown https://www.anchorterminal.com/tools/wordpress.md · JSON https://www.anchorterminal.com/api/v1/tools/wordpress.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:
- Schema & documentation, 85 against 65
- Security & auth, 77 against 62
- Transparency & trust, 80 against 68

Also in its favour:
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- Free to start without a card
- No incidents deducted, where WordPress loses 5 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

### WordPress (B)

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 35

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 | DatoCMS | WordPress | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 80 | 78 | DatoCMS +2 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 85 | 65 | DatoCMS +20 |
| Agent ergonomics | 13% (16.2 this run) | 78 | 74 | DatoCMS +4 |
| Security & auth | 14% (17.5 this run) | 77 | 62 | DatoCMS +15 |
| Payments & pricing | 10% (12.5 this run) | 35 | 60 | WordPress +25 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 81 | 83 | WordPress +2 |
| Transparency & trust | 7% (8.8 this run) | 80 | 68 | DatoCMS +12 |
| Negative events | ≤15 | 0 | -5 | |
| **Total** | | **74.4 · BB** | **64.8 · B** | |

## Facts side by side

| Fact | DatoCMS | WordPress |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Dato Srl | WordPress.org (open-source project) |
| Hosted endpoint | `https://site-api.datocms.com` | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Free |
| 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 | GPL-2.0-or-later. The MCP Adapter plugin is GPL-2.0-or-later too |
| Tools exposed | 9 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| Last release | 2026-10-01 | 2026-10-06 |
| Terms last updated | couldn't be read | no document linked |
| Privacy policy last updated | couldn't be read | no date given |
| Customer content may train models | couldn't be read |  |
| Terms restrict automated access | couldn't be read |  |
| Terms restrict benchmarking | couldn't be read |  |
| Terms or service can change without notice | couldn't be read |  |
| Arbitration or class-action waiver | couldn't be read |  |
| Popularity | 153k npm/wk | 21k stars |

## 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.

**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

### 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

### WordPress

1. 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
2. Send the Application Password as Basic auth over HTTPS only. Core disables Application Passwords on plain HTTP outside a local environment
3. Upload a file with POST `/wp-json/wp/v2/media` first, then set `featured_media` or reference the returned URL in the post content
4. To roll back, GET `/wp/v2/posts/<id>/revisions/<rev>?context=edit` and POST its title and content to the post. There's no restore route
5. Pass `_fields=id,status,link,modified` on lists and read X-WP-TotalPages. `per_page` stops at 100

## Questions

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

DatoCMS scores 74.4 (BB) on agent readiness against WordPress's 64.8 (B), and leads in 5 of 7 scored categories. WordPress leads on payments & pricing.

### Do DatoCMS and WordPress need an API key?

DatoCMS takes an API key or an OAuth sign-in. WordPress needs an API key.

### Can an agent call DatoCMS and WordPress without installing anything?

DatoCMS has a hosted endpoint at https://site-api.datocms.com. WordPress runs on your own machine, with no hosted endpoint listed.

### Are DatoCMS and WordPress open source?

No open-source release is listed for DatoCMS. WordPress is open source (GPL-2.0-or-later. The MCP Adapter plugin is GPL-2.0-or-later too).


## For agents

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

## Other comparisons with DatoCMS or WordPress

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