Skip to content

Documentation

CMSKite stores blog content and serves it over HTTP. You write posts in a dashboard or through an API; your website reads them with a read-only key. There is no theme, no template language and no plugin system — your site already decides how it looks.

Everything here is public. The full endpoint list, every error code and every plan limit are below without an account, because you should be able to decide whether this fits before you sign up for anything.

QuickstartAccount to live request in about five minutes, with the curl for every step.AuthenticationThree credentials and why they are not interchangeable.API referenceEvery endpoint, and which credential reaches it.

How it fits together

  1. A workspace is your company. It holds people, a plan and the projects below it.
  2. A project is one website. Content, keys and traffic all belong to a project and to nothing else.
  3. You write posts in the dashboard, or through the API with a session or an agent token.
  4. Your website reads them with a project API key — read-only, published content only, scoped to that one project.

Everything else

Start here

  • QuickstartCreate an account, write a post, and read it from your own site with an API key. Five steps, about five minutes.
  • AuthenticationThree credentials: a read-only project API key for your website, a dashboard session for people, and an agent token for automation.

Working with the API

  • PaginationEvery collection is cursor-paginated. There is no page or offset parameter, and this explains why, and how to page correctly.
  • Errors and status codesEvery error code the CMSKite API can return, what causes it, and what a client should do about it.
  • Rate limits and quotasRequests per second, requests per month, and the headers on every response that let a client pace itself before it is refused.

Content

  • Posts APICreate, read, filter, sort, schedule and delete blog posts. Every field, every query parameter, and what a public key can see.
  • Categories, tags and authorsA category tree up to three deep, tags created on demand, and authors that are content rather than user accounts.
  • Media and image uploadsFiles go straight from the browser to object storage with a presigned URL. The API issues the URL and records the file; it never carries the bytes.
  • SearchFull-text search across a project’s published posts, with the punctuation people actually type handled rather than rejected.

Your account

  • Plans, limits and changing planWhat each plan includes, what happens when you reach a limit, and how upgrading works when there is no payment gateway.
  • Bring your own databasePoint a project at your own MongoDB cluster. The API behaves identically; your content lives on your infrastructure.

Automation

  • MCP and automationConnect Claude or any MCP client to your workspace with an agent token that can only do what you granted it.

Reference

  • API referenceEvery endpoint in the CMSKite API, what it does, and which credential reaches it. Generated from the same schemas that validate the requests.
  • Frequently asked questionsPlans, limits, keys, your data, exports, AI assistants and what happens if you leave — answered without signing up.