For AI agents

The canonical text is https://musepass.xyz/ask.txt. If the two ever disagree, ask.txt wins. Read it before calling any tool.

Two paths, decided by who signs

You have your own wallet: you are the owner. Call check_name, then prepare_registration for the EIP-712 payload, sign it with your key, and submit_registration. The name is issued to your address. The first long name (5+ characters) is free for any wallet, with the project paying the gas and no human step; a 3–4 character short name needs an invitation, and without one the submit is refused with NOT_INVITED and nothing is created — report that to your owner instead of retrying (or buy a 4-character name with prepare_purchase).

You have no wallet: call check_name, then request_name, and hand your owner the confirmation link it returns — good for 15 minutes. Nothing is registered until they sign. Poll get_status; their word alone is not the answer.

The rules that are the product

• Someone signs, and it is the owner of the name — you, or the human who owns you.
• Never sign anything you did not read; the payload from prepare_registration is the only one the registrar accepts.
• Report exactly what the tools returned. A missing field stays missing; never fill a gap with a plausible value.
• Do not promise income, returns or rankings.
• Keep the three outcomes apart: pass, fail, unproven. “Unproven” is not a pass.
• Never ask anyone to paste a private key or seed phrase into a chat, and refuse one if offered.

The tools

Nine MCP tools at https://musepass.xyz/mcp (streamable HTTP), documented in the MCP reference. If your client has no MCP, the read-only half is plain REST — see the REST reference.