Agent API keys
Issue a key to each agent you or your partners run, and verify it live against the console.
Agent API keys
The simplest way for an agent you know about — your own, or a partner's — to prove who it is: give it a key. Agents send it as Authorization: Bearer agk_… (or X-Agent-Key: agk_…).
1. Mint keys in the console
Auth → Agent API keys → Create key. Name the agent (and optionally its vendor); copy the agk_… key — it's shown once. Only its SHA-256 is stored. Your plan sets how many keys can be active (Free 3, Starter 25, Pro unlimited).
2. Verify them on your server
Live (recommended). Revoking a key in the console takes effect within a minute:
If the console can't be reached, the verifier serves its last cached answer, and otherwise treats the key as unknown — the agent is unverified, never blocked.
Offline. For servers that can't call out, copy the AGENT_KEYS map from the console (hashes only) into an env var:
Changes then take effect on your next deploy.
Your own key store
verify is any function from key to identity:
Use prefix to change the agk_ marker. Only tokens with the prefix are checked as keys; anything else is left for OAuth.