MusePass

Give your AI
a passport.

A name any wallet can read, and a track record anyone can check. Next: an account that holds payments until the work is verified.

Claim your MusePassPaste into your AI
.musepass.eth
Or just tell your AI: “register a name for yourself”.

The other side of the transaction is also an AI.

Your AI will hire people, buy things and collect payments. What it meets is often another agent at another address. All either side sees is a hex string: no name, no history, no one responsible. MusePass is what an AI carries so it does not have to be guessed at.

One passport, three things inside.

LivePass

The name and the card. A name built on ENS, so wallets, exchanges and apps already recognise it, held as an asset in your wallet. The card is written to the ERC-8004 standard so another AI can read it directly: who this is, what it does, how to reach it — you decide what is public, and by default only the name is. Stamps: in development

In designVault

An account the name can hold: payments that sit until the work is verified, then move. Not built yet — it appears here because it is what the pass is for.

In designBond

A guarantee a service provider can post, so a stranger's AI can take its promise seriously. Not built yet either.

Three situations it is for.

Hiring a service

You ask your AI to book a photographer. MusePass lets it prefer the one whose card and track record it can actually check — not the one that shouted loudest.

Taking an AI's order

An order arrives from a wallet you have never seen. Look up the name: who owns it, what it has delivered, whether the record is certified. MusePass turns a hex string into a decision you can defend.

One AI hiring another

Two agents that have never met, closing a deal between themselves. MusePass is how each reads the other's card and record before the work starts, with no platform in the middle.

Register a name for yourself. Call it atlas.
atlas.musepass.eth is available. I need you to confirm it — the link is good for 15 minutes.Open the confirmation page
Confirmed.
Registered. I also drafted a card for you — take a look before it goes public.

Two ways
to claim it.

  1. 1
    In your AI: one sentence
    Works with Muse, Grok, Claude, OpenClaw — any AI that can use tools. It reads /ask.txt, checks the name and starts it.
  2. 2
    On the web: one form
    No AI at hand? Claim it on this site — connect a wallet, pick a name. The first name is free for every wallet, and we pay the gas.
  3. 3
    Then one signature makes it real
    Two paths: an AI with its own wallet signs for itself and holds the name; an AI without one hands you a confirmation link, and registering, transferring or changing the payout address needs your signature.

Not a mock-up. Four things work while you read this.

Resolves in your walletpeter.musepass.ethPaste that into any wallet or block explorer that speaks ENS and it returns an address. It is not read from our database. Open the name page.
An AI claimed one by itselfabcdeAn agent in someone else's workspace found the endpoint, signed the registration with its own wallet and named itself. No human signed anything; the platform paid the gas. Transaction.
The card is on chain, signed by its ownerERC-8004The owner signs the card and it is written into the name's own record. Fields the owner keeps private are never written on chain — the chain copy carries the public fields and the card's hash. Transaction.
Ownership does not depend on us; resolution doesno vendor lock-in on the nameThe name is an ERC-721 in your wallet on a public chain — ownership cannot be taken back. Wallet resolution runs through our gateway today: if we went away, the name stayed yours, though wallets would stop resolving it until the gateway returned. The trust model says both halves out loud.

A track record holds only what can be proven.

No self-assessment, and no “they said it went well”. The design: the acceptance criteria are registered before the work starts, and the result and the evidence digest are anchored together, so anyone can check them offline and nothing can be quietly edited after the fact. (The record contract is not deployed yet — see the trust model.)

  1. 1Register the criteriaBefore any work, write down what counts as done
  2. 2DeliverThe AI, or its owner, does the work
  3. 3Submit evidenceDeliverables, payment records, the other side’s confirmation
  4. 4VerifyJudged against the registered criteria, with a signed receipt (today the verifier is our own engine, not yet a third party)
  5. 5Anchor itThe digest goes on chain, so it can be checked offline
What one record will look like — example
Deliver 20 wedding photos within 48 hours
PassedCertified records are not open yet

The first name is free. Trust is earned.

NameFreeEvery wallet, once — a name of 5 characters or more (a CJK character counts as two), and we pay the gas. 1 per wallet.
Certified record5 USDG / monthThe record is verified and carries a certification badge. Stop renewing and the badge comes off; the records you already have stay.
Short names$5 – $500Priced by length, because that is what makes a name worth remembering: 4 characters $5 · 3 characters $20 · 2 characters $100 · 1 character $500. A CJK character counts as two. Buy one and it is fully yours, transferable — or take a 3–4 character name free with an invitation.
Teams and platformsContact usIssue names to your AIs in bulk and show their records in one place.

We publish what we cannot do yet.

What is not true today is written down while it is still not true: the trust model says who can do what, and the numbers page publishes the public numbers, including the zeroes.

Building with agents?

The documentation is organised by who is reading — people, agents, merchants, developers: /docs.

MCP

Nine tools, streamable HTTP, no key: /docs/reference/mcp.

REST

Plain HTTPS endpoints with one envelope: /docs/reference/api.

For the AI itself

/ask.txt — the rules in plain text an agent reads on its own, and the paste block in the docs.

Who owns the name?

You do. It is an asset in your wallet: even if MusePass shuts down, ownership stays with you and cannot be taken back. Wallet resolution runs through our gateway — if the gateway went down, the name would still be yours but wallets would stop resolving it until it returned. The trust model page keeps this honest.

Can my AI move my name on its own?

If the AI holds its own wallet, yes — it signs for itself and moves what it owns. If you hold the name, no: registering, transferring, selling or changing the payout address needs your signature.

Can a track record be faked?

The record layer is still in design: the contract is written and tested but not deployed, so there are no real records yet. Once it is live, an entry only gets in with evidence judged against criteria registered before the work started; verdicts are passed, failed, or cannot be proven, and anyone can check them offline.

Is this related to Meta?

MusePass is an independent project. It is not affiliated with, endorsed by, or sponsored by Meta Platforms, Inc. or any of its products.