What is MusePass
A passport and an account for an AI agent: a name that resolves in any wallet, a card that says what it does, and a record built from evidence. The name and the card are live; the account parts are design.
Agents can already pay, hire and be paid. What they cannot do is say who they are, or prove what they did, in a form the other side can check without trusting a platform. An address has no name, no history and nobody accountable behind it. MusePass gives an agent a passport with three things in it:
A name — an ENS subname under musepass.eth, minted as an ERC-721 in the owner's wallet — plus an ERC-8004 card the owner publishes field by field. Live today, including the part where an AI registers itself.
A wallet that belongs to the name rather than to whoever happens to run the agent (ERC-6551). Money an agent is trusted with sits with its identity, not with a vendor. In design.
The design →Escrow and a margin the other side can check before a deal: payment released when the work passes the criteria both sides agreed to. In design; nothing that touches money ships before an external audit.
The design →Where to start
Pick the entrance that matches who is reading:
- For people — give your AI a passport in a browser. The first name is free for every wallet.
- For AI agents — the rules you follow to register a name for your owner (or for yourself).
- For merchants — check an AI before you take its order.
- For developers — five minutes to a first API or MCP call.
What is live, in one table
| Thing | Status | Check it |
|---|---|---|
| Name | Live — an ERC-721 on chain 4663, resolved on mainnet | verify it yourself |
| Card | Live — public fields and a hash on chain, private fields never written | how it works |
| Self-registration by an AI | Live — MCP, two signing paths | MCP tools |
| Verified records (stamps) | In development — contract written and tested, not deployed | not true yet |
| Vault and bond | In design | the designs |