An AI-native headless CMS you run entirely through a REST API — define content types, publish entries, and read them back with a handful of calls. Already have a codebase? The CLI below can detect the schema instead.
New here? POST /api/auth/register then /api/auth/login gets you the $JWT step 01 uses below — or create an account from the dashboard instead.
POST a project, then POST a content type with the fields an entry needs. Nothing is detected — you tell the API what a blog post looks like, and it’s live as a schema immediately.
curl -X POST $CMS_API_URL/api/projects \
-H "Authorization: Bearer $JWT" -H 'Content-Type: application/json' \
-d '{"name":"My Blog","slug":"my-blog"}'
curl -X POST $CMS_API_URL/api/projects/my-blog/content-types \
-H "Authorization: Bearer $JWT" -H 'Content-Type: application/json' \
-d '{"name":"Blog Post","slug":"blog-post","fields":[
{"name":"Title","slug":"title","type":"TEXT","required":true},
{"name":"Body","slug":"body","type":"RICH_TEXT","required":true}
]}'Create a draft entry and publish it — from the dashboard, a script hitting the same endpoints, or an AI agent through MCP.
curl -X POST $CMS_API_URL/api/projects/my-blog/content/blog-post/entries \
-H "X-API-Key: $CMS_API_KEY" -H 'Content-Type: application/json' \
-d '{"slug":"hello-world","data":{"title":"Hello, World","body":"..."}}'
curl -X POST $CMS_API_URL/api/projects/my-blog/content/blog-post/entries/<id>/publish \
-H "X-API-Key: $CMS_API_KEY"A public, CDN-cached endpoint serves published entries as JSON. Whatever renders your site fetches from here, no SDK required.
curl $CMS_API_URL/api/v1/content/my-blog/blog-post/hello-world \
-H "X-API-Key: $CMS_READ_KEY"Create a free account — the dashboard and the API calls above run on the same login.