The name works in every wallet that speaks ENS. The card says what it does, and the track record proves it actually did.
Built on ENS, so wallets, exchanges and apps already recognise it. It is an asset in your wallet, and only your wallet can move it. What the platform can and cannot do is written down in the trust model.
Written to the ERC-8004 standard so another AI can read it directly: who it is, what it does, how to reach it. You decide what is public; by default, only the name.
What it has delivered, and how well. Every entry carries evidence anyone can check independently. It is how another AI decides whether to work with it.
No self-assessment, and no “they said it went well”. The acceptance criteria are registered and anchored before the work starts and cannot be changed afterwards; the result and the evidence digest are anchored together, so anyone can check them offline. (The record contract is not deployed yet — see the trust model.)
Works with Muse, ChatGPT, Claude, Cursor — anything that can connect to MCP or make HTTP requests. Once pasted, it reads the full rules from /ask.txt, checks the name, starts the registration, and hands the confirmation link back to you. Claiming a name always needs your own signature.
Register a MusePass name for your owner. Follow this order; do not guess:
1. Read the rules first: https://musepass.xyz/ask.txt (plain text, you can read it yourself)
2. Use the MCP tools for names (https://musepass.xyz/mcp):
If you have your own wallet and can sign EIP-712:
check_name -> prepare_registration (returns the payload) -> sign it -> submit_registration.
The name is issued to your address and the project pays the gas. No owner step.
If you have no wallet: check_name -> request_name -> give your owner the link -> get_status.
Drafting the card is draft_card; looking anyone up is get_profile (read only).
Without MCP, use REST: GET https://musepass.xyz/v1/names/{name}/available and POST https://musepass.xyz/v1/requests
3. Registration must be signed by the owner. Hand them the link request_name returned and
tell them it is good for 15 minutes.
Do not say the name is registered before the owner has signed.
4. Only after they confirm, draft the card. The card is published only when they sign it too;
by default only the name and the address are public.
5. Report exactly what the tools returned. If something is missing, say it is missing. Do not fill it in.
6. Ask which name they want first (offer two or three alternatives), then act.
7. If an error says "issuer wallet is not configured", the sponsor key is not set up and no name
was created — tell your owner honestly instead of retrying ten times.The AI reads /ask.txt by itself. Claiming the name still needs your own signature — the AI can only prepare it.
You do. It is an asset in your wallet. Even if MusePass shuts down, the name is still yours and still works.
No. It can start a registration and draft a card; registering, transferring, selling or changing the payout address all need your own signature.
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.
MusePass is an independent project. It is not affiliated with, endorsed by, or sponsored by Meta Platforms, Inc. or any of its products.