Skip to main content
Oathera logo Oathera
Use casesFive stories: no identity, a new identity, impersonation, cloning, and a call outside the boundary. PlatformOathera Agent Enrollment, the Oathera Identity Service and Oathera Agent Enforcement. FeaturesWhat Oathera does for you, grouped by purpose. IntegrationsYour identity provider, your MCP servers, your cloud. SecurityHow Oathera fails closed, and what it doesn't do.
Developer sectionComponents, the identity token, standards and settings. Data sheetsThe buyer and developer data sheets, as PDFs. LearnGuides on giving AI agents an identity of their own. GlossaryPrincipal, sponsor, anchor key, key digest, identity token. SimulatorWatch a stolen token, a replayed proof and a tampered call get refused.
About usThe team and the mission behind Oathera. BlogPosts from the Oathera team. CareersOpen roles at Oathera. ContactTalk to the founders, or become a design partner. LinkedIn ↗Oathera on LinkedIn.
Privacy PolicyHow we handle data. Terms of ServiceTerms for using Oathera. Data Processing AgreementOur DPA for customers. Sub-processorsThird parties we rely on.
Become a design partner

Learn · Keys

Proof of possession for AI agents: anchor keys, session keys and operation proofs

Proof of possession means a caller must show it holds a key, not just a token. For an AI agent, Oathera uses three layers: an anchor key kept on the agent's host, a session key held only in memory and rotated at every token issuance, and a single-use operation proof signed for each call.

On this page

  1. Why a token alone is not enough
  2. The three keys and proofs
  3. How this relates to DPoP and mTLS
  4. How Oathera helps
  5. FAQ

Why a token alone is not enough

A bearer token works for whoever holds it. Copy it from a log, a prompt or a config file and the copy is the agent. A token that names a key, and calls that must be signed with that key, turn a stolen token into a dead string. This idea is also called sender-constrained credentials.

The three keys and proofs

  • Anchor key. An Ed25519 key created and kept on the agent's host, in a file only the agent's user can read. Its key digest is the agent's identity. It can be held in KMS, HSM, TPM or a secure enclave. It signs token requests and the key-binding that names each new session key.
  • Session key. A new Ed25519 key made in memory at each token issuance, never written to disk, replacing the last one. The identity token, valid at most five minutes, names it.
  • Operation proof. Before each call the agent signs a single-use proof over the operation, its arguments and the token, with a nonce used once. Replayed or altered proofs are refused.

How this relates to DPoP and mTLS

DPoP and mTLS are standard ways to bind an OAuth token to a key or a certificate. Oathera does not use DPoP: the operation proof plays that role for each tool call, and also covers the arguments, which a transport-layer binding does not. Oathera signs its own HTTP calls with RFC 9421. The identity is the anchor key's digest (RFC 7638), and tokens carry the session key as a confirmation claim (RFC 7800).

How Oathera helps

Oathera Agent Enforcement refuses a token sent as a bare credential, a token without its session key, a replayed proof and tampered arguments. The agent signs each proof on its own host. A copy of the agent on another machine does not match the host recorded at enrollment and gets no token.

Oathera does not verify people, judge model output, inspect or rewrite prompts, or replace your identity provider. Your identity provider and proofing sources do the first; Oathera is the layer under them for agents.

FAQ

What is proof of possession for AI agents?

Requiring the agent to prove it holds a key on every request, so a copied token cannot be used by anyone else.

What is a non-exportable anchor key?

The agent's long-lived key, created on its host and not moved elsewhere. It can be held in KMS, HSM, TPM or a secure enclave so the key material itself cannot be exported.

Does Oathera use DPoP or mTLS?

No. The single-use operation proof does the job of DPoP for each tool call and also covers the call's arguments.

How often do session keys rotate?

At every identity token issuance. Tokens last at most five minutes, and sixty seconds for privileged capabilities.

Related: Per-agent identity vs shared API keys · Stop token theft and replay · Standards map for AI agent identity

Become a design partner Watch the simulator More guides

← Back to Learn
Oathera logo Oathera

Every AI agent, sworn in. Oathera gives every AI agent an identity bound to the machine it runs on, with a named person who answers for it, and checked every time it acts.

Product

  • Use cases
  • Platform
  • Features
  • Integrations
  • Security

Developers

  • Developer section
  • Data sheets
  • Learn
  • Glossary
  • Simulator

Company

  • About us
  • Blog
  • Careers
  • Contact
  • GitHub

Legal

  • Privacy Policy
  • Terms of Service
  • Data Processing Agreement
  • Sub-processors
© 2026 Oathera Inc. · All rights reserved
Know Your Agent (KYA)

Cookie preferences

We use cookies to run this site and, with your consent, to understand usage and improve Oathera. Strictly necessary cookies are always on; you can choose whether to allow analytics and marketing cookies below.

Read the privacy policy

  • Strictly necessaryAlways on

    Required for the site to work, security, load balancing, and remembering your cookie choices. These cannot be switched off.

  • Help us measure traffic and see how the site is used, so we can improve it. No personal profiles are built.

  • Used to make messages about Oathera more relevant across other sites. Off unless you turn it on.