The SEO content API for AI agents
You already know where your content needs to publish. CopyJump gives your app or agent the researched SEO content, metadata, and workflow context it needs to get it there.
CopyJump creates the content. Your system decides where it goes.
This is for teams with their own website, CMS, publishing workflow, or coding agent. Use CopyJump for the content engine, then publish through the system you already control.
What the API preview is for
Start with the pieces an external agent actually needs: content, calendar context, jobs, keywords, internal links, and brand-safe access.
Content API
Read finished CopyJump content and metadata so your own app can publish it where it belongs.
Calendar API
Read planned content and create scheduled work so your publishing system knows what should be generated next.
See the calendar →Agent Jobs
Create content jobs for the CopyJump agent, check their status, then fetch the finished draft when it is ready.
See the agent →Keyword Workflows
Use CopyJump keyword research outside the app so your agent can find the right opportunity before it requests a draft.
Explore SEO →Internal Links
Carry CopyJump internal link context into your publishing layer instead of rebuilding site-aware link logic in every CMS.
Brand-Scoped Keys
Keep access narrow and predictable with keys designed around one brand context at a time.
Built for agent-led publishing workflows.
CopyJump handles the research and content workflow. Your tools handle the final mile: formatting, technical SEO, CMS import, and deployment.
Request the work
Your app or agent asks CopyJump for content, chooses a calendar slot, or starts from a keyword opportunity.
Let CopyJump write
CopyJump handles brand context, SEO structure, internal links, and the agent workflow behind the draft.
Publish your way
Your stack imports the finished content into Next.js, WordPress, a headless CMS, or your own deployment pipeline.
Give your agents a serious SEO workflow.
The content endpoint exists today. The broader preview will build around the same REST shape, with MCP support planned for tools like Claude Code and OpenAI Codex.
Keep using the AI tools your team already likes.
Give them CopyJump content, brand context, keyword data, and publishing state instead of asking them to guess from a thin prompt.
- Current: read finished content and metadata.
- Preview: create and check content jobs.
- Preview: use calendar and keyword context from the same workflow.
GET https://app.copyjump.com/api/v1/content?status=published&synced=false
Authorization: Bearer cj_live_...
{
"data": [{
"id": "content_abc123",
"title": "How to choose an SEO workflow",
"status": "published",
"agent_generated": true,
"is_internal": false,
"synced": false,
"created": "2026-04-10T14:20:00Z",
"updated": "2026-04-12T09:15:00Z"
}],
"total": 42,
"limit": 20,
"offset": 0
}API Preview FAQ
Is the CopyJump API live today?▼
The content endpoint exists today, and the broader public API is in early preview planning. Request access if you want to shape the first version or test it with your publishing workflow.
Will this work with MCP clients?▼
That is the plan. The REST API comes first, and the MCP server will expose the same content, calendar, keyword, and job workflows.
Can my agent publish to WordPress or Next.js?▼
CopyJump provides the content layer. Your agent or app can adapt the output to WordPress, Next.js, a headless CMS, or your deployment flow.
Will webhooks be available?▼
Webhooks are being considered for job-complete notifications. The first version may start with polling to keep the API simple.
Want CopyJump inside your publishing workflow?
Tell us what you want to build, what stack you publish with, and whether you need REST, MCP, or both.
Request API Access