ZevContent Docs
Open dashboard
Developer documentation

Your content,
modelled by you.
Served as JSON.

Define your own content types, or start from a built-in blog and knowledge base we maintain for you. Writers work in a dashboard; your frontend reads one REST API. No renderer, no theme, no opinion about how your site is built.

Read your first content Read the API reference

Request 

GET /v1/content/team-member
  ?where[role]=engineer
  &sort=name
  &limit=2

Authorization: Bearer sk_…

Response

200 OK 
{
  "data": [
    { "id": "ent_2c8Rk…",
      "values": {
        "name": "Ada",
        "role": "engineer",
        "photo": { "url": "https://…", "width": 800 }
      } }
  ],
  "meta": { "limit": 2, "has_more": true,
            "next_offset": 2, "next_cursor": null }
}
From key to content

Three steps.
None of them is npm install.

There is no SDK to install and no build step to add. A key and curl are enough to see everything a project holds, which is also all an AI agent needs to write the integration for you.

Read the full quickstart
~ read some content 
# 1. Create a project at dashboard.zevcontent.com and
#    copy a key. There is nothing to install.
export API=https://api.zevcontent.net
export ZEVCONTENT_KEY=sk_...

# 2. Ask the API what this project holds.
curl "$API/v1/introspection" \
  -H "Authorization: Bearer $ZEVCONTENT_KEY"

# Every content type with its fields and response shape,
# every built-in module with its endpoints, and the rules
# for paging, filtering, rate limits and errors. One
# request, and you know the whole contract.

# 3. Read the content.
curl "$API/v1/blog/articles?limit=5" \
  -H "Authorization: Bearer $ZEVCONTENT_KEY"

# Bylines, categories and SEO arrive RESOLVED — no second
# request per article, and no fallback chain to reimplement.
When you're ready

Read the reference.

Every endpoint, every query parameter, every error code. And when you hold a key, the API describes itself — one call to /v1/introspection returns your project's whole contract as JSON.

Open the API reference
Introduction For AI agents Error catalogue Releases