Skip to content

API keys

Every Kifas request authenticates with a bearer token. There’s exactly one auth method in MVP:

Authorization: Bearer kifas_live_<24-char-random>
Mode Prefix Example Behavior
Live kifas_live_ kifas_live_aB3... Production traffic. Full quotas.
Test kifas_test_ kifas_test_xY9... Sessions capped at 5 min. The docs sandbox uses this mode.

The full key is shown once at issuance. We store the argon2id hash; if you lose the key, revoke it and mint a new one.

Scope Grants
org:read Read organization metadata
project:read / project:write List/get projects / create/modify
session:create Start sessions, drive them
run:read Read run results, artifacts
mcp:tools Invoke any MCP tool (broad — use scoped grants in production)

Default keys carry session:create + mcp:tools + project:read + org:read. You can mint scoped keys from Settings → API keys.

  • Rotate: create a new key, swap it into your client config, then delete the old one.
  • Revoke: delete the key. Effective immediately; in-flight calls fail with unauthorized.

OAuth 2.1 + Dynamic Client Registration (the MCP-spec auth flow) is on the roadmap; bearer keys are the only auth path in MVP.

When you click Run on a code sample in these docs, the docs server auto-issues a test-mode key tagged metadata.purpose='docs_sandbox' (one per org, reused on every sandbox call). It appears in Settings → API keys as “Docs sandbox (auto-issued)” — revoke it like any other key. The next sandbox click will mint a fresh one.