Announcing Dome Managed Agents.

Try it now

Identity providers for AI agents

Your identity provider already knows your people. Dome verifies that identity on every agent call, so rules and audit name the person an agent acted for.

Any OIDC identity providerRegister its issuer once, and every agent call carries a verified person.

Integration catalog
IntegrationKindGoverned byStandard
Auth0 access tokens verified on every agent call, so rules read the user's email and custom claims.
IdentityAccessOIDC
Clerk
IdentityAccessOIDC
Google ID tokens verified on every agent call, so rules read the person's email and Workspace domain.
IdentityAccessOIDC
Keycloak tokens verified on every agent call, so rules read the person's groups and audit names them.
IdentityAccessOIDC
Entra access tokens verified on every agent call, so rules read app roles and audit names the person.
IdentityAccessOIDC
Okta tokens verified on every agent call, so rules and audit name the person each agent acted for.
IdentityAccessOIDC
Ping Identity
IdentityAccessOIDC
1–7 of 7

Any OIDC issuer, two steps

Register the issuer with Dome, then have agents pass the user's token with each call. Dome needs no credentials for your identity provider.
  1. 1

    Register a verification provider

    Dome reads the issuer's signing keys from its discovery document.

    shell
    dome verification-providers create \  --name corporate-idp --method oidc \  --oidc-url https://<issuer> \  --oidc-expected-audience <client-id>
  2. 2

    Pass the user's token

    The agent keeps its own Dome key and adds the person's token as a header.

    python
    client = OpenAI(    base_url=f"{GATEWAY_URL}/v1",    api_key=DOME_AGENT_KEY,    default_headers={"X-Dome-Act-As": user_token},)

Commands tested against a Dome workspace on September 30, 2026.

Common questions

Which identity providers work?
Any OIDC issuer that signs tokens with RS, ES, PS, or EdDSA keys works, and HMAC-signed tokens are refused.
What does Dome read from the token?
The sub and email claims, plus groups and roles wherever your IdP puts them. Map other claims in the verification provider, and rules and audit see them too.
Is this the same as signing in to Dome?
No. Dashboard sign-in is Enterprise SSO, and an agent acts for a person only when it sends that person's token.

Talk with ourFDE team.

Or start free, and register your first agent in minutes. Connect it through a gateway, give it rules, and see every call it makes in one audit trail.

Talk with our FDE team

Our engineers design, build and run governed agents for the part of your business you want to change. You see what they deliver.

Access

How agents, people and the apps that call them are identified, and how that identity reaches every decision.

Every agent you run, under one system of control.