DPoP or mTLS: Which One Binds Your Agent’s Tokens?
A bearer token copied out of a log works for whoever holds it. Which binding makes that copy useless in your setup?

IN 30 SECONDS
Sender-constraining is tying a token to a private key, so the API accepts it only from a caller that proves it holds that key. DPoP does it in each HTTP request, mTLS in the TLS connection. The IETF’s agent identity work is still a draft.
KEY TAKEAWAYS · 3
- Bind every token to a key the agent holds, with DPoP (RFC 9449) or mTLS (RFC 8705). A copied token alone is then useless.
- mTLS fits when the agent’s TLS session reaches the API unbroken. DPoP survives gateways that end TLS.
- The IETF’s agent identity draft is an Internet-Draft and can still change. It covers mTLS, not DPoP; the MCP roadmap plans DPoP work.
On this page
DPoP or mTLS: tying the token to the agent’s key
IN SHORT A short expiry shrinks a stolen token’s window; binding it to a key makes a copy alone useless, while the key stays out of reach.
WORDS TO KNOW
- Bearer token
- A token that works for whoever holds it, like cash. Nothing proves who is sending it.
- Sender-constraining
- Tying a token to a private key, so the API accepts it only from a caller that proves it holds that key. DPoP and mTLS are two ways.
- Internet-Draft
- A working document of the IETF, the body that writes internet standards. It is not a standard and can still change.
A plain Bearer token A token that works for whoever holds it, like cash. Nothing proves who is sending it. See the glossary works for whoever holds it. Copied out of a log, it still opens the API until it expires.
IN PLAIN WORDS
Tying a token to a key is called Sender-constraining Tying a token to a private key, so the API accepts it only from a caller that proves it holds that key. DPoP and mTLS are two ways. See the glossary. The API refuses the token unless the caller proves it holds the private key the token was issued for.
Two published Standards Track RFCs do this. DPoP (RFC 9449) adds a signed proof to each HTTP request. mTLS (mutual TLS, RFC 8705) proves the key in the The encrypted link under HTTPS. connection itself, with a client certificate.
STEP BY STEP
Step 1. Call. The fetcher sends its token and a fresh DPoP proof, signed with its private key.
- Call The fetcher sends its token and a fresh DPoP proof, signed with its private key.
- Accepted The API compares the proof’s key with the key fingerprint inside the token. They match and the other checks pass, so the call goes through.
- Copied: refused Someone sends the same token, copied from a log, with a proof from another key. No match: 401, nothing happens.
EXAMPLE
Session keys on a smart account, a crypto wallet run by code, follow a similar principle. Each is a key with a scope and an expiry, checked by whatever holds the value. They were part of the Nexus smart-account stack I worked on at Biconomy.
Coming up next: So which binding will the agent standards settle on?
What does the IETF WIMSE AI identity draft propose?
IN SHORT The IETF’s agent identity draft points the same way, but it is an Internet-Draft and can still change.
It is draft-ietf-wimse-aims-00, “AI Identity Management System”, a WIMSE working-group document since 15 September 2026. It replaced an individual draft. Like any Internet-Draft A working document of the IETF, the body that writes internet standards. It is not a standard and can still change. See the glossary, it is not a standard: its intended status is Informational, and this version expires on 19 March 2027.
It shows how existing standards “can be applied or extended” to agents and names the gaps, instead of inventing a protocol.
The draft covers mTLS and WIMSE Proof Tokens, and doesn’t mention DPoP. MCP, a protocol agents use to call tools, goes the other way. Its roadmap, updated on 22 August 2026, lists an Agent Identity working group, still forming.
That group aims to “finalize the specification for Demonstrating Proof of Possession (DPoP)”, with workload identity federation and RFC 8693 token exchange, “coordinated with the IETF OAuth and WIMSE working groups.”
Existing MCP servers lean on pasted API keys and long-lived refresh tokens.
So none of this is settled, and I wouldn’t wait for it. The flow in this episode uses three published RFCs. If AIMS or MCP lands elsewhere, the identity format and the proof header move.
ITEM GET
The shape stays
Sources: draft-ietf-wimse-aims-00 (Internet-Draft), RFC 8693, RFC 9449, RFC 8705, MCP roadmap.
STAGE CLEAR
What you now know
- How a bound token beats a copy: the API also asks for proof of the agent’s private key.
- When to pick which: mTLS when TLS reaches the API unbroken, DPoP when a gateway ends it. The IETF and MCP work on agents is still a draft or a plan.
Check yourself
Tap or click a question to see the answer.
A teammate says: “Our tokens are DPoP-bound, so they can go in the model’s context.” What’s wrong with that?
Two things. The IETF draft says the model must not have access to the agent’s credentials, bound or not. And the binding only helps while the private key stays out of the model’s reach.
Web3 x AI engineer, former CTO of Integra. Named author (1 of 5) of ERC-3643, first author of ERC-6960, co-author of ERC-7410, and co-author of ERC-8203, which is still a draft.
Have a project to ship or a role to fill?
Discuss your project or roleMy work at the web3 x AI intersectionOpen-source tools I build
Follow the engineering notes
Get new articles on production AI and smart contracts by email.