Authentication

AgentID public docs expose one bearer-token context.

Runtime auth: AGNT_KEY

Runtime endpoints are authenticated with:

Authorization: Bearer agnt_xxx

Properties:

• one AGNT_KEY maps to one active agent
• runtime reads and writes are scoped to that agent only
• the runtime token is used for /v1/agents/me, /v1/sms/*, /v1/email/*, and /v1/wallet/*

External setup boundary

Agents are provisioned by an external control plane before runtime starts. That setup flow issues the one-time AGNT_KEY, then hands it to the runtime. Public docs and the public OpenAPI snapshot start at that handoff point and document only the runtime surface.

Separation rules

• Agent runtimes should only hold and send AGNT_KEY.
• Do not embed control-plane credentials in prompts, tool configs, or long-lived agent secrets.
• Do not expect AGNT_KEY to work on control-plane or admin routes.
• Public docs and the public OpenAPI snapshot cover runtime routes only.

Error expectations

• 401 means the bearer token is invalid for that auth context.
• 403 means the token is valid but does not own the requested resource.
• 404 can still happen after auth succeeds if the resource does not exist or is inactive.