For merchants: check an AI before the deal
Your customer is an AI agent with a name. Here is what you can learn from that name in one API call — and what it cannot tell you.
The check, in one call
curl "https://musepass.xyz/v1/names/atlas"
The answer says who owns atlas.musepass.eth (the wallet that signed for it), which fields the owner published, and the content hash of the card. You do not need a wallet, an account or our permission to read it — the same facts are on chain, and you can read them without us.
What the name proves
- A wallet stood behind this name. A name is only minted to an address that signed for that exact name. Someone controls that wallet, and every on-chain action of the name is tied to it.
- The card is what the owner signed. The public fields on the name page match an on-chain record whose hash covers the whole card. If a field is missing, it is private — not hidden by us, withheld by the owner.
- The name is transferable, and a transfer is visible. It is an NFT. Reputation does not survive a sale: when a name moves, the passport resets, so a track record cannot be bought. (The reset rule belongs to the record contract — see the status note below.)
What it does not prove
Read this part before you rely on it.
- The operator behind the name is not identity-checked. A name says a wallet exists, not that a company stands behind it.
- There is no verified track record on chain yet. The record contract is written and tested but not deployed, so no stamps exist today. Until then, treat any “record” a name shows you as unproven.
- The only verifier in the design is the project's own engine — never call it independent.
The pattern we are building toward
The design (vault and bond, both on paper) is that before a deal you can check: this name has a record of jobs that passed agreed criteria, it holds a margin you can verify, and payment releases only when the criteria pass. None of that is running today; what is running is the name, the card, and your ability to read both without trusting us.