Authentication
Getting and using API keys.
DeeCee.ai supports two auth methods:
- OAuth (Sign in with DeeCee.ai) — MCP server only. Preferred for Claude and other MCP clients.
- API keys (
dc_live_...) — REST API and MCP server. Use for scripts, backend services, and header-based connectors.
REST stays API-key only. Its callers can't complete an interactive sign-in.
OAuth for MCP clients
The MCP server at https://api.deecee.ai/mcp accepts OAuth access tokens issued by DeeCee.ai's sign-in service. Clients discover it from the protected-resource metadata at https://api.deecee.ai/.well-known/oauth-protected-resource/mcp.
- Add
https://api.deecee.ai/mcpas a connector in your MCP client. - Choose OAuth / sign-in when prompted.
- Sign in to DeeCee.ai and approve access.
Registered redirect URIs:
| Client | Redirect URI |
|---|---|
| Claude.ai / Claude Desktop | https://claude.ai/api/mcp/auth_callback |
| Claude Code | http://localhost/callback or http://127.0.0.1/callback (any port) |
Revoke access any time by removing the connector in your client.
Getting a key
- Sign in to DeeCee.ai and go to Settings → API Keys
- Click Create API Key, give it a name (e.g. "Claude Desktop"), and pick a mode
- Copy the key immediately — it's shown exactly once and can't be recovered later. If you lose it, revoke it and create a new one.
Key format
dc_live_a1b2c3d4e5f6... (live mode — real usage, charged against your quota)
dc_test_a1b2c3d4e5f6... (test mode)Using a key
Every request — REST or MCP — needs the key as a Bearer token:
curl https://api.deecee.ai/v1/frameworks \
-H "Authorization: Bearer dc_live_..."For MCP clients (Claude Desktop, Cursor, etc.), the same header is set in your client's connection config — see the Claude Desktop quickstart.
Revoking a key
Back in Settings → API Keys, click the trash icon next to any key. Revocation is immediate — any integration using that key loses access on its next request. This can't be undone; create a new key if you need to reconnect.
Scoping
Keys are scoped to your individual DeeCee.ai account — every decision, job, and credit charge made with a key belongs to the user who created it. There's no team or organization sharing in the current version.