WordPress.com API
WordPress.com runs a fully public REST API across /rest/, /wp/ (core), and /wpcom/ namespaces, the same surface that powers Calypso and the official mobile apps. Access is self-serve with OAuth2 or Application Passwords. Rate limits exist but are never published as numbers.
Frequently asked questions
WordPress.com scores A on Supergood's API Report Card. WordPress.com runs a fully public REST API across /rest/, /wp/ (core), and /wpcom/ namespaces, the same surface that powers Calypso and the official mobile apps. Access is self-serve with OAuth2 or Application Passwords. Rate limits exist but are never published as numbers.
WordPress.com has a workable official integration path. Most engineering teams can build against it directly. Open API: self-serve, documented, with SDKs
WordPress.com is the Automattic-operated, commercially-hosted version of the open-source WordPress content management system.
Vertical: horizontal website building / managed CMS hosting / digital publishing (classified as 'misc' because WordPress.com is industry-agnostic and spans creators, bloggers, SMBs, agencies, ecommerce stores, and enterprise publishers rather than serving a single regulated vertical). A creator, small business owner, or agency signs up on wordpress.com, picks a plan (Free through Commerce), registers a domain (free first year on paid plans), and selects a theme or uses the AI website builder to generate a starter site.
9/10. WordPress (the open-source CMS) powers ~43% of all websites globally and holds ~61.8% of the CMS market as of early 2025.
Yes, for the sites running on it, WordPress.com is the system of record for the entire content and (on Commerce plans) commerce stack: all posts, pages, custom post types, media assets, comments, user accounts and roles, taxonomy (categories, tags, custom taxonomies), navigation menus, theme customizations, newsletter subscriber lists, Jetpack-collected analytics, contact-form submissions, WooCommerce orders, products, customers, payments (via WooPayments/Stripe), and the full audit history of edits.
WordPress (open-source) was first released May 27, 2003 by Matt Mullenweg and Mike Little. Automattic was founded in 2005 to commercialize WordPress, with WordPress.com launching as the hosted product the same year.
WordPress.com REST API rate limits are not publicly documented as specific numeric values, developers must reverse-engineer them from 429 responses. Rate limits hit hard in headless CMS configurations where JavaScript frontends make many API calls; shared hosts and WordPress.com lower tiers enforce strictly, producing HTTP 429 errors. Full sourced list under Sources below.
Common alternatives include Wix, Squarespace, Webflow, Shopify, Ghost, Substack. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
WordPress.com scores GOOD on MCP availability. WordPress.com documents official MCP support in its developer docs, including a tools reference and instructions for connecting custom MCP clients, and Automattic maintains the mcp-wordpress-remote server on GitHub. The feature is labeled beta but the docs and repos are active.
Yes. WordPress.com publishes an official MCP server, so MCP clients like Claude, Cursor, and Codex can connect to it directly. Setup instructions are in the vendor's documentation.