On this page
Authentication
Send your key on every request:
X-API-Key: sk_live_xxxxxxxx
Content-Type: application/json
Do not use Authorization: Bearer for API keys.
Keys
| Prefix | Created in | Works with |
|---|---|---|
sk_live_… | API & MCP | https://api.scaliq.ai/public/v1 |
Invalid or revoked key → 401 unauthorized.
Who can use the API
| Allowed | Not allowed |
|---|---|
| Paid ScaliQ (Stripe / AppSumo) | Free / trial |
| Shared team members (owner-scoped) | Frozen team members |
Workspace data is always the owner’s. Max 5 API keys per workspace (default).
A key created by a team member stops working as soon as that member is frozen or removed from the workspace (401 unauthorized), even though the key still exists. Ask the workspace owner to create a replacement key.
Manage keys
app.scaliq.ai/api-mcp — create, list (lastUsedAt), delete to revoke. Secret shown once on create.
Claude / ChatGPT vs Cursor
| Client | How you authenticate |
|---|---|
| Claude / ChatGPT (OAuth Sign-in) | Sign in on /mcp-authorize → Allow (client name + redirect host; Deny exits without minting) → workspace key MCP OAuth is minted/rotated. Do not put that key in Cursor mcp.json. |
| Cursor / static MCP | A different key from /api-mcp in mcp.json X-API-Key (any name other than MCP OAuth — that name is reserved). |
| REST / n8n / scripts | Any workspace key from /api-mcp via X-API-Key. |
OAuth reconnect in-place rotates MCP OAuth (same key slot). Other Claude sessions on the old secret must reconnect; Cursor keys stay valid when kept separate.