Learn · Identity
How to make a named person accountable for an AI agent
An agent nobody stands behind is an agent no one is accountable for. Enrollment approval ties every agent to the named person who approved it before it can act, and keeps that link in the agent's enrollment record.
Why a named person matters
Autonomous software still acts on someone's behalf. If an agent deletes a table or emails a customer, the first question is always who stands behind it. Without a person recorded at enrollment, that question has no answer and accountability evaporates. With Oathera, every agent that has an identity has a principal: the person who approved its enrollment. A sponsor, the person or organization answerable for the agent's scope, is a separate role, and Oathera records a verified sponsor for it.
Enrollment approval
The link to a person is established at the moment an agent is enrolled. The agent's Oathera Agent Enrollment requests enrollment; a principal signs in through your identity provider, is shown the clearance requested for the agent, and approves it. Until that enrollment approval happens the agent holds no usable identity, and Oathera Agent Enforcement refuses its calls. This single checkpoint is what makes the resulting identity meaningful: it was granted deliberately, by a principal, rather than minted automatically.
No approval, no identity. An agent nobody approved gets no identity token, so Oathera Agent Enforcement refuses its calls to the tools behind it.
Keeping the approval on record
The approval is written into the agent's enrollment record at the Oathera Identity Service: the principal who approved it, as your identity provider named them, with the agent's key and host. When the Oathera Identity Service is set to issue them, the credential service (VCI) also records it as verifiable credentials. Every identity token carries the principal, so you can show the chain from a specific action back to the agent and from the agent back to the person who answers for it.
The sponsor, the person or organization who answers for the agent, can be someone other than the principal. Oathera records a real, named sponsor for each agent, verified through your own proofing sources.
How to set it up
- Enroll through your IdP. The agent requests enrollment; your own IdP identifies the principal who approves it.
- Approve once, explicitly. The principal reviews the agent and approves the enrollment. Before then, the agent has no identity token.
- Bind the approval to identity. The approval is recorded in the agent's enrollment record, and as a verifiable credential (VCI) when credentials are switched on.
This is how Oathera handles enrollment. See the platform or the use case.
FAQ
How do you assign a human sponsor to an AI agent and make that accountable?
Enroll the agent through an enrollment approval step: a principal signs in through your identity provider and approves the enrollment before the agent can act, and the approval is written into the agent's enrollment record. Every later action traces back through the agent to the person who approved it. Oathera records a separate, named sponsor for each agent.
What stops an agent from running without a sponsor?
A fail closed default. The agent holds no usable identity until a principal approves its enrollment, so an agent nobody approved cannot get an identity token, and Oathera Agent Enforcement refuses its calls to the tools behind it. Calls that never reach Oathera Agent Enforcement, for example with a borrowed key, are outside what Oathera checks.
What happens when the person who approved an agent leaves?
Revoke each of their agents: a revoked agent gets no new identity token, and its next enforced call is refused. Or deprovision the person, so that the Oathera Identity Service refuses tokens and boundary decisions to all of their agents without touching their own sign-in. Oathera also learns departures from your identity provider.