Content your team can run.
A headless CMS with the blog and knowledge base already built, and an API your developers will not fight.
- Already built
- Blog and help centre
- Your images
- In your own bucket
- Price today
- Free, no card
Built for four different people.
Find yourself, and skip the argument written for everybody else.
Start from a template, not a blank page.
The sections a site actually has, already modelled. Pick one, rename a field, start writing.
Stop rebuilding the blog.
And the help centre, the media library, the release process, and the webhooks that tell your site when any of it changed.
- 01 Blog
A blog you do not have to model.
- 02 Knowledge base
A help centre that stays navigable.
- 03 Custom content
Model the things only you have.
- 04 ZevAI
A second pair of eyes on the draft.
- 05 Media
Images stay in storage you own.
- 06 Releases
Version the whole project, then promote.
- 07 Webhooks
Your site finds out the moment it changes.
Ask ZevAI, then decide.
Rewrite a sentence, change its tone, proofread a page. Every suggestion arrives as a tracked change you accept or reject, so nothing moves without you.
- 1 Ask Select a sentence, a paragraph or the whole page.
- 2 Decide Take the change, or leave it. Nothing saves until you do.
Built for agents
An API that explains itself.
An MCP server exists to translate for an API that cannot describe itself. This one can, so an agent reads the project and starts working in a single request.
What an agent can do- No MCP server
- Nothing to install, host or keep in step with the API.
- One call, whole model
- Types, fields, response shapes, routes and events.
- Errors that teach
- A refusal names the fields that would have worked.
- Keys with a limit
- Scope an agent to one project and an expiry it can read.
$ curl https://api.zevcontent.net/v1/introspection
What comes back
- Every
- content type and field
- Every
- endpoint and response shape
- Every
- webhook event
One request, and an agent knows the whole project. No adapter, no SDK, nothing to keep in step.
Your content, in your stack.
REST and JSON with a bearer token. No client library to install, no build step to add, nothing to keep in sync with a schema.
- Next.js
- Astro
- Nuxt
- React
- Vue
- Svelte
- Laravel
- Remix
Anything that speaks HTTP works, including the ones not listed. See the quickstart
Live on ZevContent.
A cybersecurity company and a magazine about album covers. Two content models with nothing in common, one API, both in production.
-
Exsol SolfieldA cybersecurity company publishing three security assurance products, the frameworks they map to, and an insights library.
Custom types for products and frameworks, the blog for insights.
-
The Cover JournalA visual culture publication about the people and ideas behind album cover art.
Custom types for covers, artists and creatives, the blog for the journal, and link fields for a menu that survives a rename.
Frequently asked questions
A few answers to the questions we hear most often.
What does ZevContent cost?
It is free while we are in beta, with no card required to start. Paid plans arrive when we ship them, and existing projects will not be cut off without notice.
Where are my images stored?
In your own object storage bucket, not ours. ZevContent holds the connection and signs uploads; the files stay in a bucket you own on ZevCloud, Amazon S3, Cloudflare R2, or any S3-compatible store. If you use ZevCloud you can connect a bucket in two clicks without handling a key.
Do I have to build a blog schema myself?
No. A blog and a knowledge base are built in, with articles, authors, categories, tags, SEO fields and rich text already modelled. Custom content types are for the things that are specific to your product, not for rebuilding a blog for the fifth time.
Can an AI agent set up a project on its own?
Yes, and without an MCP server or any other adapter. GET /v1/introspection returns the whole map in one request: every content type with its fields, the exact response shape of each one, every endpoint, every webhook event, and the relationships between types. Writes go through the same REST surface a website reads from. Errors name the fix rather than the failure, so an agent corrects itself without a human reading the docs.
Does ZevContent have AI writing tools?
ZevAI sits in the editor: rewrite a sentence, change its tone, shorten or expand it, proofread a page, or generate a summary and SEO description from what the page already says. Every suggestion appears as a tracked change, with the old text struck through and the new text highlighted, so nothing is written until somebody accepts it. The workspace owner decides which members have it.
How do writers publish without breaking the site?
Roles decide it. A writer edits and saves drafts but cannot publish. An editor publishes. A developer changes the structure. Nobody is shown a button their role would refuse.
Can I change the content model without breaking what is live?
Releases. Build the new structure and content in a release, point a preview deployment at it, then promote it in one atomic step. Readers see the old version, then the new one, never half of each.
How does my site know when something changes?
Signed webhooks, nineteen events covering entries, content types, media and releases. Every delivery is an HMAC over the raw body, and every event names its subject and the path to re-fetch, so you invalidate one page rather than dropping a whole cache.
Is there a way to link content without hardcoding URLs?
Yes, and it is the fix for menus that break. A link field stores the id of a blog article, category, author, or knowledge base entry, and resolves the current title and slug on every read. Rename the category and every menu that points at it follows.
Start with a project and a key.
Free while we are in beta. Paid plans when we ship them, and never a surprise bill.