# ZevContent developer documentation

> ZevContent is a headless content backend: you model your content in a dashboard, writers fill it in, and your frontend reads it over a REST API. It ships three BUILT-IN MODULES — a blog, a knowledge base and a shared author directory — whose schema we define and maintain, alongside CUSTOM CONTENT TYPES you define yourself. This file is a curated index of every doc page — follow the `.md` link beside any title to grab that page's clean markdown body.

Drop the whole site into one context window with `https://docs.zevcontent.com/llms-full.txt`, or fetch any single page's markdown by appending `.md` to its URL (e.g. `https://docs.zevcontent.com/api/authentication.md`).

IF YOU HOLD AN API KEY, START WITH THE SERVER, NOT THIS SITE. `GET https://api.zevcontent.net/v1/introspection` with that key returns the whole project as JSON: every content type with its fields and response shape, every built-in module with its endpoints and shapes, the rich text contract, and the conventions for authentication, pagination, filtering, rate limits and errors. It describes THAT project rather than the product in general, so it cannot be out of date with the content you are about to read. See `https://docs.zevcontent.com/api/introspection.md`. These pages explain the reasoning behind what that response contains.

## Getting started

- [Introduction](https://docs.zevcontent.com/guide.md): What ZevContent is, what it is not, and the one decision you make before anything else.
- [Quickstart](https://docs.zevcontent.com/guide/quickstart.md): From a key to real content in three requests. Nothing to install.
- [API keys](https://docs.zevcontent.com/guide/keys.md): Two kinds of key, what each one may do, and why the browser gets its own.
- [For AI agents](https://docs.zevcontent.com/guide/agents.md): Read this first if you are an agent holding a key — the API describes itself, and that description is better than this site.
- [Troubleshooting](https://docs.zevcontent.com/guide/troubleshooting.md): The failures people actually hit, and what each one is really telling you.

## Concepts

- [Content types and entries](https://docs.zevcontent.com/concepts/content-model.md): Singletons, collections, the ten field types, and what a response looks like.
- [Releases](https://docs.zevcontent.com/concepts/releases.md): Version control for content, why custom types have it and built-in modules do not.
- [Rich text](https://docs.zevcontent.com/concepts/rich-text.md): One document, three views, and a node schema that is ours rather than an editor's.
- [Media and images](https://docs.zevcontent.com/concepts/media.md): Your bucket, your bytes. Public and private projects, and why a static build must ask for permanent URLs.
- [SEO](https://docs.zevcontent.com/concepts/seo.md): One resolved object on every page-shaped thing, with the fallback chain already applied.

## API reference

- [Overview](https://docs.zevcontent.com/api.md): One base URL, one key, and the whole surface on one page.
- [Authentication](https://docs.zevcontent.com/api/authentication.md): Bearer keys, what each kind may do, and the failures that look like authentication and are not.
- [Pagination and filtering](https://docs.zevcontent.com/api/pagination.md): Every listing pages, nothing returns everything, and filtering happens in the database.
- [Rate limits](https://docs.zevcontent.com/api/rate-limits.md): Three separate budgets, counted per key, with headers that let you slow down before you are refused.
- [Errors](https://docs.zevcontent.com/api/errors.md): One envelope, a stable code to branch on, and a message written to be acted on.
- [Introspection](https://docs.zevcontent.com/api/introspection.md): One request that returns your project's entire contract — the most useful call in the API.
- [Content](https://docs.zevcontent.com/api/content.md): Reading and writing your own content types — the /v1/content and /v1/schema endpoints.

## Built-in modules

- [Blog](https://docs.zevcontent.com/modules/blog.md): Articles, categories and a resolved SEO chain — a built-in module you configure nothing for.
- [Knowledge base](https://docs.zevcontent.com/modules/knowledge-base.md): A help centre with a navigation tree, freshness dates and helpful/not-helpful voting.
- [Authors](https://docs.zevcontent.com/modules/authors.md): One directory of people, shared by every module that credits anybody.