Api Index

Bluesky Copilot API

Drive Bluesky Copilot from Claude, an MCP client, a script, or anything else that can make an HTTP request: your post analytics, AI post ideas grounded in your real history, drafts, and scheduling.

API access is part of the paid plan.

Base URL — https://bskycopilot.com/api/public/v1

One key, one account

An API key belongs to exactly one Bluesky account. Whatever you send, the account is decided by the key — there is no handle parameter anywhere, and supplying one changes nothing.

If you run several Bluesky accounts, create one key per account. Agents call GET /me/ with each key to learn which handle it drives, so they can say "post to @alice" rather than juggling tokens.

Getting a key

  1. Go to Settings.
  2. Under API keys & agents, name the key after whatever will use it — "Claude Desktop", "my publishing script" — so you know what you are revoking later.
  3. Choose a scope:
    • Read only — analytics, stored suggestions, and prompt export. Cannot change anything, and cannot spend your AI credit.
    • Read and write — also drafts, scheduling, and the AI actions.
  4. Copy the key. It is shown once and never again. We store only a hash of it, so if you lose it, revoke it and make another.

Revoking takes effect immediately: anything using that key stops working on its next request.

The free path

Two endpoints spend your own Anthropic or OpenAI credit. Two return the exact prompt those endpoints would have sent — with your real posts already filled in — and cost nothing at all.

If the thing calling the API is itself an AI agent, it should almost always use the prompt. It runs the prompt itself, you pay nothing, and you do not even need an AI key configured. Our MCP server and Claude skill both default to this.

Where to go next

For an agent that reads documentation directly, point it at /llms.txt — the whole API in one plain-text file.