# The AI-native CMS for sites you built with AI. > The AI-native CMS for sites built with Claude Code, v0, Astro, or Next.js. One signed route, one prompt to set up, and an agent that runs your blog. Source: https://contengi.com/ai-native-cms AI-native CMS Claude Code, v0, or Cursor built the site in a weekend. Contengi gives it a CMS and a blog agent through one signed route, set up from one prompt, so nobody opens a code editor to fix a typo again. [Request beta access](https://contengi.com/beta-access) [Interactive demo](https://contengi.com/demo)$50 / MONTH · BYOK · NO LOCK-IN Signed publish200 OK POST/api/contengi X-Contengi-Timestamp1790000000 X-Contengi-Signaturesha256=9f2c…e41a { "title", "slug", "seo\_title", "meta\_description", "excerpt", … } → { "url": "yoursite.com/blog/retainer-pricing" } Works with whatever built your site Claude Codev0CursorNext.jsAstroSvelteKitRemixVercelNetlifyCloudflare Definition ## What is an AI-native CMS? 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 Installing an admin theme or plugins Designing a content model up front A second login for whoever writes Opening the repo to fix a typo ## Connected in four steps, one of them a prompt. 1. 01 ### Add your site In Settings, add a custom website with the endpoint URL, for example yoursite.com/api/contengi. Copy the signing secret. 2. 02 ### Paste the prompt Claude Code or v0 builds the endpoint against the contract, in whatever stack your site already uses. 3. 03 ### Add the secret Save it as CONTENGI\_SIGNING\_SECRET in your hosting environment, then deploy. 4. 04 ### Hit Test Contengi sends a signed test post. A 200 with a URL means your blog is live. The contract ## One endpoint, and it covers the whole lifecycle. 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 titleslugseo\_titlemeta\_descriptionexcerptbody\_htmlfaqauthor\_namefeatured\_image POST Publish or update PATCH Unpublish to draft DELETE Remove the post ## Three ways to give an AI-built site a blog. Bolt on WordPress Setup A second site on a subdomain, or a rebuild Who writes You Editing The WordPress admin Fits an AI-built site Awkwardly, it brings its own front end Where posts live WordPress database Headless CMS Setup Design a schema, add the SDK, wire up previews Who writes You Editing The CMS studio Fits an AI-built site Well, if a developer sets it up Where posts live The vendor’s content store Contengi Setup One route from one prompt Who writes Agents in your brand voice, you approve Editing The Contengi CMS, an edit agent, or your own Claude Fits an AI-built site Built for it Where posts live Your own database or content store 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 ## The Claude that built the site can edit the blog. 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 ## Common questions ### What is an AI-native CMS? 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. ### Which builders and stacks does it work with? 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. ### What if my site is fully static? 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. ### Do I need to know how to code? 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. ### Where does my content live? 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. ### Is it secure? 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 ## Related features and reads In the platform [### Websites built with Claude The build prompt and the full contract.](https://contengi.com/integrations/claude-websites) [### v0 websites One route handler, added from one prompt.](https://contengi.com/integrations/v0-websites) From the blog [CMS for AI-native websites: the guide for 2026 and 2027](https://contengi.com/blog/cms-for-ai-native-website) [CMS for Vercel websites](https://contengi.com/blog/cms-for-vercel-websites) [Which CMS to use with a v0 website](https://contengi.com/blog/cms-to-use-with-v0-website) [Where your content lives after Claude Code builds the site](https://contengi.com/blog/claude-website-cms) [What is a headless CMS, and do you need one?](https://contengi.com/blog/what-is-a-headless-cms) [See all posts](https://contengi.com/blog) ## Your site took a weekend. Your blog can keep up. One prompt to connect, and an agent that writes, edits, and publishes in your brand voice. [Request beta access](https://contengi.com/beta-access) [Try it out](https://contengi.com/demo)