API and MCP server

Auth

Create a key under Settings → API keys, read-only or read-and-write. Send it as Authorization: Bearer aeo_….

Quickstart

curl -s https://getkeats.com/api/v1/offerings \
  -H "Authorization: Bearer $KEATS_API_KEY"

curl -s https://getkeats.com/api/v1/offerings/$OFFERING/read \
  -H "Authorization: Bearer $KEATS_API_KEY"

curl -s https://getkeats.com/api/v1/actions/$ACTION/brief \
  -H "Authorization: Bearer $KEATS_API_KEY"

curl -s -X POST https://getkeats.com/api/v1/actions/$ACTION/complete \
  -H "Authorization: Bearer $KEATS_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"url":"https://example.com/new-page","publishedAt":"2026-11-12","notes":"New page answering the question"}'

The full spec: /api/v1/openapi.json (OpenAPI 3.1).

MCP

Streamable HTTP at https://getkeats.com/mcp, the same keys. Claude Code:

claude mcp add --transport http keats https://getkeats.com/mcp --header "Authorization: Bearer aeo_…"

Other clients:

{
  "mcpServers": {
    "keats": {
      "type": "http",
      "url": "https://getkeats.com/mcp",
      "headers": {
        "Authorization": "Bearer aeo_…"
      }
    }
  }
}

Prompts: weekly_review, work_action, tune_prompts. Resources: aeo://offerings/{id}/read and aeo://offerings/{id}/answers.

Rules

• Auth: send a workspace key as Authorization: Bearer aeo_…. Make keys in the app under Settings → API keys (owners and admins). A key works in its own workspace only; another workspace's ids answer 404, as if they didn't exist. Read-only keys get 403 on writes.
• Errors are JSON: {"error": {"code", "message", "hint"}}. The hint says what to do next. Codes: invalid_input 400, unauthorized and key_revoked 401, forbidden 403, not_found 404, method_not_allowed 405, conflict 409 (the app's rules refuse it now, e.g. a card can't jump the board), plan_required 402 (the workspace's trial hasn't started: a person opens the error's url to start it with a card), plan_limit 402 (the plan has no room for what you're adding, or adding is paused; the message has the numbers and the hint the fix), idempotency_mismatch 422, rate_limited 429, internal 500.
• Rate limits: 120 requests and 30 writes a minute per key (MCP counts each request, and each write tool). Over a limit you get 429 with Retry-After; every REST response carries X-RateLimit-Limit, -Remaining and -Reset.
• Inputs are strict: a field an operation doesn't take is refused by name (invalid_input), never ignored.
• Lists return {"data": [...], "nextCursor"}; pass cursor=<nextCursor> for the next page and limit (1–200, default 50).
• Writes take an optional Idempotency-Key header: a retry with the same key and body gets the first response again (for 24 hours); the same key with a different body is refused.
• Long work returns a job, never a held connection: add_brand, read_site_again, prepare_offerings and run_now. Poll GET /api/v1/jobs/{jobId} (get_job) every 30–60 seconds; each job says what to call next.
• Plans: tracked questions and brands count against the workspace's plan (get_plan, get_usage). Every write made with a key is recorded: the key, the operation and what it acted on.

Operations