The problem
Drafts now come from people and agents, in docs, chats and CMS fields. Without one place to run it all, the same questions come up every week.
How PMKIN solves it
Every piece of content takes the same path, whether a person or an agent writes it.
Ideas, drafts and due dates sit on one shared planner, so everyone can see where each post is.
Answers “Did the webhooks guide ever get published?”
A brief holds the keyword, audience and outline. One teammate or agent claims it and writes from it.
Answers “Who’s writing the pricing post?”
Every draft lands in a review queue. Approve it, or send it back with notes the agent reads.
Answers “Can someone check it before it goes live?”
Search Console data shows what readers look for and where you’re close to page one.
Answers “What are we writing next month?”
Content planning
Every document lives on a board with a column per status, and on a calendar by its due date. Drag a card to move it along.
Group related posts into topic clusters, and PMKIN shows how far each topic is, like “3 of 8 published”.
Briefs
A brief says what to write: the target keyword, the audience, the outline and the posts to link to. Fill in what helps.
Mark it ready and a teammate or an agent claims it. Only one can, so two agents never write the same post.
MCP server
Connect Claude, ChatGPT, Cursor or any MCP client in a couple of minutes. Agents read your project, plan ideas, claim briefs, write drafts, add images and send their work to review.
They can't touch API keys, members or billing. And every change they make shows which agent made it, and for whom.
Reviews
Drafts from people and agents land in the same review queue, with a note for the reviewer. Approve to publish, or request changes and say what to fix.
SEO data
Connect Google Search Console and PMKIN imports your clicks, impressions and rankings every day, matched to your documents.
It points out searches where you rank just off page one, and suggests real queries as keywords when you write a brief. Your agents can read the same data.
For developers
Your site fetches published documents over the GraphQL delivery API and renders them however you like: a blog, docs or a changelog. Drafts, briefs and reviews stay inside PMKIN.
Automate the rest with the management API, or build on the same tools your agents use.
import { GraphQLClient, gql } from 'graphql-request'const query = gql`query ListDocuments {documents(includeDrafts: false) {idisPublishedmetaDescriptionmetaTitlepublishedAtslugsubtitletitle}}`const client = new GraphQLClient('https://content.pmkin.io/graphql', {headers: {Authorization: `Bearer ${process.env.PMKIN_API_KEY}`}})const { documents } = await client.request(query)
Start for free, invite your teammates, and connect your first agent in a couple of minutes.