Capa documentation
Guides and reference for building with Capa, editing in it, and running it for clients.
Capa is a hybrid headless CMS. Your team writes and publishes in the admin, and your sites, apps and agents read the content through a cached API.
Pick a path
I build sites and apps
Create a model, publish an entry, mint a key and make your first read in five minutes.
I write and publish content
Your first day in the admin: find an entry, edit it, publish or schedule it.
I run Capa for clients
Set up a client project: roles, one key per site, and a clean handoff.
I connect an AI agent
What an agent can read and do today, the MCP server, and which key to give it.
Reference
API reference
Hosts, headers, the response envelope, and the dated /api/ read API.
Entries
Choose fields with select, filter, sort, page, and expand relations.
GraphQL
Typed reads, limits, query cost and persisted queries.
SDK
@capacms/sdk: the typed client, codegen and the Next.js helpers.
Error codes
Every error the API returns, what it means and how to fix it.
Legacy API
The /v2/api and /v3/api reads that existing sites still use.
For agents
These docs are also plain Markdown. /llms.txt lists every page, /llms-full.txt holds all of them in one file, and any page is available as Markdown by adding .md to its URL, like /docs/api/entries.md.