API and MCP
The same data as the app pages, as JSON. Part of the Pro and Team plans.
Authentication
Create a key under Account, API keys. Keys start with cj_live_ and are shown once. Send the key on every request:
Authorization: Bearer cj_live_YOUR_KEY
The header X-Api-Key: cj_live_YOUR_KEY works too.
curl -s https://chartjump.com/api/v1/apps/calai/creatives \
-H "Authorization: Bearer cj_live_YOUR_KEY"Rate limits
REST and MCP calls share the daily count, which resets at 00:00 UTC. Every response carries X-RateLimit-Limit and X-RateLimit-Remaining. Over the limit you get HTTP 429.
REST endpoints
Base URL https://chartjump.com. All responses are JSON.
App slugs are the last part of a page URL, for example calai in https://chartjump.com/app/calai.
Errors
{ "error": { "code": "plan_required", "message": "The API and MCP are part of the Pro and Team plans." } }
MCP server
Chartjump runs a remote MCP server (Streamable HTTP, protocol 2025-06-18) at
https://chartjump.com/mcp
Tools:
Claude Code
claude mcp add --transport http chartjump https://chartjump.com/mcp \
--header "Authorization: Bearer cj_live_YOUR_KEY"
Claude Desktop
Add this to claude_desktop_config.json (Settings, Developer, Edit config) and restart Claude Desktop. It uses mcp-remote to pass your key.
{
"mcpServers": {
"chartjump": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://chartjump.com/mcp",
"--header",
"Authorization:${CHARTJUMP_AUTH}"
],
"env": {
"CHARTJUMP_AUTH": "Bearer cj_live_YOUR_KEY"
}
}
}
}
Then ask, for example: "Use Chartjump to find Cal AI and list its five longest-running ads with their hooks."
Terms for API use
- Keys are personal to your account. Do not share them or put them in client-side code.
- Do not republish the data as a competing database, and do not resell creator data.
- Do not use the data to contact or profile individual creators at scale.
- When we tell you a record was removed, delete it from your copies.
- Full rules are in the terms.