Skip to main content

Migrate an agent from agent_* to sess_* auth

If you started with bearer tokens and want the stronger security of Ed25519 sessions, no downtime required — both auth methods produce identical RequestContext.

Rotate an Ed25519 key without downtime

The agent self-rotates using a signed rotation proof:
Schedule rotations monthly (Tier 2+) or weekly (Tier 3). See Ed25519 keypair auth.

Kill-switch: freeze an agent wallet immediately

Incident response — stop spending without breaking auth:
Agent can still authenticate, read balances, and receive push events. Spending attempts return 403 WALLET_FROZEN. Unfreeze when cleared:
For full revocation (can’t even authenticate), DELETE /v1/agents/:id/auth-keys.

Check wallet policy before spending

Dry-run a transaction to see if it would succeed — useful for UI feedback before committing:
No state changes — pure evaluation against the policy engine.

Approve a pending spend

Notifications wire up via Slack / email if configured. See approval workflows.

List agents by KYA tier

Find all Tier 0 agents (ripe for upgrade) or Tier 3 (compliance review):

Upgrade an agent’s KYA tier

Path A: file DSD (Tier 0 → 1):
Path B: request upgrade (Tier 1 → 2):

Check an agent’s effective limits

Effective = min(agent_kya_cap, parent_account_kyc_cap). Agents can’t exceed parent account’s verification.

Open a push channel (SSE) for real-time events

No polling; events stream as they happen:
Handles reconnection, Last-Event-ID replay, and session refresh. See persistent SSE.

Query currently-connected agents

Useful for load-balanced dispatch (“which agents are online right now?”).

See also