Works with whatever built your site
Definition
An AI-native CMS is a content management system built for websites that AI tools created and AI agents keep up to date. It lives outside your code, connects through one small endpoint your AI builder writes, and hands the writing, editing, and publishing to agents while you approve.
Sites built with Claude Code or v0 go live fast and ship without an admin panel. Contengi becomes that admin panel, with an agent in it that knows your brand.
What you skip
In Settings, add a custom website with the endpoint URL, for example yoursite.com/api/contengi. Copy the signing secret.
Claude Code or v0 builds the endpoint against the contract, in whatever stack your site already uses.
Save it as CONTENGI_SIGNING_SECRET in your hosting environment, then deploy.
Contengi sends a signed test post. A 200 with a URL means your blog is live.
The contract
Publishing sends a signed POST, and your site upserts the post on its slug. Unpublishing sends a signed PATCH that takes the post back to draft, and deleting sends a signed DELETE. Contengi only reports a post as gone once your site replies 200.
Edits arrive flagged as updates with the live URL, so the post is replaced in place and the address never changes. Less moving parts than a headless CMS, and nothing to keep in sync.
What arrives with every post
POST
Publish or update
PATCH
Unpublish to draft
DELETE
Remove the post
Bolt on WordPress
Headless CMS
Contengi
| Bolt on WordPress | Headless CMS | Contengi | |
|---|---|---|---|
| Setup | A second site on a subdomain, or a rebuild | Design a schema, add the SDK, wire up previews | One route from one prompt |
| Who writes | You | You | Agents in your brand voice, you approve |
| Editing | The WordPress admin | The CMS studio | The Contengi CMS, an edit agent, or your own Claude |
| Fits an AI-built site | Awkwardly, it brings its own front end | Well, if a developer sets it up | Built for it |
| Where posts live | WordPress database | The vendor’s content store | Your own database or content store |
Edited from Claude
Connect Contengi to Claude and every post is one chat away. Ask it to update the numbers in last month's pricing post and add an FAQ, and the edit lands in the CMS waiting for you to publish.
FAQ
A CMS built for websites that AI tools created and AI agents keep up to date. It sits outside your code, connects through one small endpoint your AI builder writes, and hands writing, editing, and publishing to agents while you approve.
Anything that can answer an HTTPS request: sites built with Claude Code, v0, or Cursor, on Next.js, Astro, SvelteKit, Remix, or Express, hosted on Vercel, Netlify, Cloudflare, or your own server.
Use a pull feed. Contengi serves your published posts as a private JSON or RSS feed behind a token, and your site reads it at build time or on request.
No. You paste one prompt into Claude Code or v0 and it writes the endpoint. The only manual step is saving the signing secret in your hosting settings.
In your own site’s database or content store, keyed on the post slug. Contengi keeps a copy of everything it publishes so edits start from exactly what went out, and your posts stay yours if you ever leave.
Every request is signed with HMAC-SHA256 over a timestamp and the body. Your endpoint checks the signature and rejects anything older than five minutes, so nobody else can post to your blog.
Keep exploring
In the platform