Browse documentation

Developer docs

Build on Cuekoo

Cuekoo turns social posts into research you can act on. Every capability is a Tool: one HTTP endpoint, one MCP tool, one schema and one credit price.

26 toolsREST + MCPCredit-based

Quickstart

Create a key, list the catalog and run your first Tool.

3 calls

API reference

Every Tool, its arguments, its result and its price.

26 endpoints

Connect an MCP client

Use Cuekoo from Claude Code, Codex, Cursor, VS Code, Gemini CLI or OpenClaw.

POST /mcp

Credits

What a call costs, and how to read your balance.

8 paid tools

One catalog, two entrances

GET /openapi/v1/tools returns the same catalog the API runs. A Tool called over REST and the same Tool called over MCP share one input schema, one output schema and one price, so an agent never needs a second integration.

curl -X POST https://api.cuekoo.com/openapi/v1/tools/list_my_accounts \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

Both calls return the same object. MCP clients address the Tool by its prefixed name, cuekoo_list_my_accounts, with the same arguments.

What you can do

  • Read connected channels, their recent posts and per-post insights.
  • Find outlier posts, search for similar creators and manage your competitors list.
  • Analyze a single post, find recurring patterns, and explain why a post worked.
  • Turn a saved idea into a draft and publish it to a connected channel.

How the API is shaped

Three rules apply across the catalog. Each has its own page, because each is where integrations usually break.

  • Authentication. One organization API key, sent as Authorization: Bearer ck_.... Keys are scoped and bound to a workspace.
  • Credits. Free Tools cost nothing. Paid Tools hold their maximum price when the call starts and settle when it finishes.
  • Queued jobs. Two Tools queue work and return a job id. Poll get_job until the result is ready.

Start building

The quickstart takes about five minutes: create a key in the workspace, call GET /openapi/v1/tools to see what the key can reach, then call a Tool.

Prefer a single file? The full HTTP surface is in openapi.json.