Skip to main content
authorization=True enables JWT verification. AgentOS also needs a public key to verify tokens against. Generate one from the control plane and wire it in.

Generate a Verification Key from the Control Plane

1

Toggle JWT authorization

Enable JWT authorization when connecting a new AgentOS, or later from the OS Settings page.
2

Copy the public key

Copy the public key for your AgentOS from the modal.
3

Set the verification key

Set the JWT_VERIFICATION_KEY environment variable to your public key in your .env file or export it directly in your terminal:
Or, if you manage keys via a JWKS file, point AgentOS at it instead:
Authorization is now active for your AgentOS.
The control plane only issues RS256 keys, which is also the default. See authorization troubleshooting for common setup issues.

Configurable Options

Configure JWT verification using AuthorizationConfig:
Use a JWKS file instead:

Environment Variables

Env vars work alongside AuthorizationConfig. Pass keys in code, env vars, or both.

Sending Authenticated Requests

Send the token in the Authorization header:

Excluded Routes

These routes are excluded from authorization checks by default: /, /health, /info, /docs, /redoc, /openapi.json, /docs/oauth2-redirect

Error Responses

Next Steps