Skip to content
Start building

Navigate

ProductDevelopersPricingDocs
Start building

PagekitBlogAI

AI agents need APIs, not admin panels

Everyone's building AI content workflows. Generate drafts, summarize posts, translate content, create social media copy. But most of these workflows hit the same wall: the CMS doesn't have a programmatic API.

So developers end up scraping their own admin panels, or building fragile browser automation to interact with their CMS. It's absurd.

The API-first approach

AI agents need to:

  • Read content programmatically
  • Create drafts without publishing
  • Update existing posts
  • Attach metadata and tags
  • Wait for human approval before publishing

All of this should be one API call. Not a browser automation script. Not a clipboard. An API.

PageKit's MCP integration

PageKit exposes its content API via MCP (Model Context Protocol), which means AI agents can:

// Read content
const posts = await blog.posts.list({ status: "draft" });

// Create a draft
await blog.posts.create({
  title: "AI-Generated Draft",
  content: "...",
  status: "draft",
});

// Wait for approval
// Human reviews in the Studio, then publishes

No admin panel scraping. No browser automation. Just an API that agents can use directly.

The future is API-first

If your CMS doesn't have a content API, it's not ready for AI workflows. Period.

← All posts