Solutions · Developers

Stop shipping copy changes

Define the content model once, wire your frontend to the delivery API, and hand the day-to-day content work to editors and their agents. No more deploys for a new field.

Part of our guide Connect a headless CMS to any frontend.

Get started See it work

GET /delivery/v1/entries/recipe?limit=10&sort=-publishedAt&depth=1
Authorization: Bearer cms_live_…

{
  "data": [
    {
      "id": "9f8cfa9c-…",
      "slug": "overnight-bagels",
      "type": "recipe",
      "publishedAt": "2026-10-29T19:10:08Z",
      "data": {
        "title": "Overnight bagels",
        "cover": { "url": "…", "width": 1600, "height": 1067, "alt": "…" }
      }
    }
  ],
  "nextCursor": null
}

REST, not glue
One GET with a bearer key, paging, filters and related entries.
Webhooks
Signed events tell your app exactly when to revalidate.
Runs on Cloudflare
One Worker with D1 and R2, and a Next.js admin.

01Models without pull requests

Content models are data. When marketing needs a new field, an admin or an agent adds it and the API serves it, without touching your repo.

02Agents in your editor

Connect Claude Code or Cursor to the MCP server and change models or seed content while you build, using the same permissions as the admin.

Questions

Which frameworks are supported?

Any framework that can make an HTTP request. The integrations guide has Next.js and Astro examples.

Back to the guide: Connect a headless CMS to any frontend

Keep exploring

Put your agent at the helm

Create a free account in a minute and connect your AI agent.

Get started