Identity
Issue one durable subject to the Agent, independent of its host.
Identity and delegated access for AI agents
Agents need identity.Not borrowed credentials.
Give every Agent a durable identity and controller-approved access to the exact APIs, scopes, and lifetime it needs.
Stable across hostsExact scopesShort-lived tokensRevocable by design
Agent Passport / Authority Flow
Host credentialsLaptop keyWorker keySandbox key
Durable Agent identity
Research Agent
- Issuer
- Realmroot
- Subject
- Immutable across hosts
One identity, many replaceable host keysVERIFIED
Explicit authority requestAwaiting approval
- Resource
- Knowledge API
- Exact scope
- articles:read
- Lifetime
- 15 minutes
Why Realmroot
Agent principals.Authority is core.
Realmroot models an Agent as its own security principal while keeping a human or organization in control of every authority decision.
Identity survives the host.
The Agent keeps one issuer and subject while host keys rotate, move, or are revoked. A machine credential never becomes the public identity.
Stable identity ≠ host credentialEnrollment grants nothing.
Establishing identity does not imply business access. A new resource, account, or wider scope always requires a new controller decision.
Identity first. Authority on request.Authority stays off the data path.
After approval, the Agent calls native or external APIs directly with a short-lived, audience-bound, DPoP-bound token.
Agent → API, directlyExplicit authority
One approval.Fully explainable.
Every grant binds one Agent to one resource, exact scopes, and a clear lifetime. Audit records reconstruct who approved what without recording credentials or raw tokens.
Read the Agent authority model →Access requestGRANT ACTIVE
Agent principalResearch Agent
≠ControllerProduct operator
- Resource
- Customer Support API
- Scopes
tickets:readdrafts:write- Lifetime
Limited · 30 min
✓ Controller approved→ Short-lived token issued
One realm, every actor
Agent-first.Not Agent-only.
People, applications, APIs, and Agents share one issuer and policy boundary. Your product stops stitching together a login system, an Agent key vault, and an authorization proxy.
One deploymentOne user poolOne issuerOne policy boundary
RealmrootIdentity root
Hosted sign-in, MFA, passkeys, sessions
OIDC clients and product integrations
Durable identity and delegated authority
Native or external protected resources
Open standards. No proprietary Agent tunnel.
OpenID ConnectOAuth 2.0RFC 8693DPoPOpenAPI
Journal
Agent identity. Explicit authority.
Why your product needs an identity root
Authentication is only the front door. A product also needs one explicit boundary for users, applications, policy, APIs, and delegated agents.
An agent identity is not an API key
Durable agent identity, host credentials, and delegated API authority solve different problems. Treating them as one secret creates accidental power.
One deployment, one realm
Why Realmroot makes the deployment—not an organization row or application record—the identity isolation boundary.
One realm. Every actor. Explicit authority.
Give your Agents a real identity.
Run one realm as the trust root for people, applications, APIs, and Agents.