Identifiable agentic payment
Let your agent use your identity.
Using x401, the open, issuer-neutral identity protocol for agentic commerce built by Proof, your agent can carry portable, reusable identity across applications. Identity says who your agent represents; authorisation says what it may do. You verify once, and your agent proves both rather than starting over at every door.
x401 INTEGRATION · IN TESTING
Identity requestAge check for the ticket vendor
18+
What the vendor asked you to prove
- Requested by
- The ticket vendor
- Shared
- Only that you are over 18
- Tickets
- Two, sent to your email
Powered by
An agent with a wallet address is anonymous by default, and anonymity is exactly what stops most real commerce. Service providers and merchants need to know who they are dealing with. Asking every one of them to run their own check, every time, is the friction that keeps agents out of regulated work.
Superfluid Wallet holds that credential on your side of the line. Your agent asks your permission to use it, presents it to the one application that asked, and demonstrates who it represents — so the transaction can be trusted without the check being run again.
Your agent already has a skill for x402, the protocol for how an agent pays. x401 answers the other half of the same question: who authorised that payment, and what they authorised it to do. A payment rail moves the money; an identity protocol says whether the party moving it is anyone at all.
It works the way the web already handles a request that needs credentials. The service answers with a challenge — the same HTTP 401 your browser meets at a protected page — but instead of a username and password it names the proof it requires. Your agent answers with a signed credential, and the service checks the issuer, the claim, the scope and the action before it proceeds.
What it does not do is hand over your identity record. Selective disclosure and zero-knowledge proofs let a credential answer only the question asked: that you are over a required age without giving your date of birth, that you may act for a company without exposing anything else about you.
And it is never the AI being vouched for. What travels is proof of the human authority behind the agent — who authorised this, and what they authorised it to do.
By your invitation
You verify.
Establish your credential once with Proof, as an individual or on behalf of a business.
Your agent asks.
When a task needs identity, your agent requests permission to use yours rather than assuming it.
You decide.
Grant or refuse. The credential is presented only to the application you allowed it for.
The service checks.
It verifies the issuer, the claim, the scope and the action before proceeding, so trust rests on the credential rather than on taking your agent’s word.
What a service can ask for under x401
Verified identity
That a verified person stands behind the request, rather than an address with nobody attached to it.
Age
That you meet an age requirement, proved without handing over your date of birth.
Membership
That you belong to a group, programme or scheme the service recognises.
Organisational affiliation
That you act for a company, without exposing anything else about you.
Signing authority
That you may commit the organisation you represent to this particular action.
Proof of humanness
That there is a person behind the agent at all — the question the rest of the web has no standard way to ask.
The claims above describe what the x401 protocol allows a service to ask for. Superfluid Wallet’s x401 integration remains under internal testing in the beta, so treat none of it as behaviour the wallet performs for you today.
Use Superfluid Wallet with your agent.
Get started