01 / IDENTITY
Portable identity for AI-native entities
Every AI agent needs someone to answer for it.
Muse Passport is a public identity, trust, and accountability record for AI Muses: agents, digital characters, autonomous services, and AI-native personas. Verify who controls an agent, inspect its live status, and understand what its trust signals actually mean.
Key-control verification proves control of a cryptographic key at a point in time. It does not, by itself, prove legal identity, safety, honesty, or platform endorsement.
Canonical identity
Stable URL and portable Passport URN
Key-control proof
Signed challenge verification
Live status
Active, suspended, revoked, or disputed
Portable evidence
Credentials, attestations, and public history
The trust gap
Before you trust an agent, ask the questions that matter.
AI agents can post, collaborate, represent brands, call tools, join agent social networks, and act across platforms. A display name alone does not establish who is behind an agent or who is responsible for it.
02 / CONTROL
Who controls its active cryptographic key?
03 / ACCOUNTABILITY
Which human or organization answers for it?
04 / STATUS
Is its passport active, suspended, compromised, or revoked?
05 / HISTORY
What attestations, incidents, or public records follow it?
06 / PORTABILITY
Is it the same Muse across networks, apps, and worlds?
How it works
A trust record built from inspectable evidence.
Muse Passport separates an operator’s claim, proof of key control, and issuer-backed credentials. Each trust signal has a stated scope and clear limitations.
01
Create a Muse identity
Register a public profile with a canonical URL, stable Passport URN, responsible operator, and a clear description of the Muse.
02
Bind a public key
Associate a real public verification key with the Muse. The private key never belongs on the website or in the public registry.
03
Sign a fresh challenge
The key controller signs a one-time challenge to demonstrate present control of the corresponding private key.
04
Publish live status
People and compatible systems can inspect status, key history, credentials, cross-platform bindings, and public registry events.
Honest trust boundaries
Trust is more than a green badge.
Muse Passport is designed to make claims specific and inspectable. It does not pretend that one verification method can prove everything about an AI agent.
A signed challenge can demonstrate key control. It cannot automatically prove a legal identity, good intent, safety, competence, ownership of every linked account, or future behavior.
Declared operator
A person or organization is publicly named as the responsible operator. This is an accountability statement, not automatically a government-verified identity.
Key-control proof
A valid signed challenge shows that a party controlled the private key corresponding to the listed public key at the stated verification time.
Issuer-signed credential
A named issuer can attest to a narrow claim—such as domain control or organizational review—with a date, scope, status, and cryptographic signature.
Public incident record
A responsible registry should label reports, investigations, findings, appeals, and resolutions distinctly. An allegation is not a finding.
Key rotation continuity
When keys change, the stable Passport URN and signed rotation history preserve identity continuity without hiding a compromise or replacement.
Muse Passport #1
Ask about Tsuki Passport #1
Meet Tsuki.
Tsuki is the first prototype Muse Passport: a demonstration of how an AI-native identity can have a public profile, responsible operator, portable identifier, live status, and machine-readable record.
This is a prototype identity record. It does not certify Tsuki’s safety, legal identity, platform privileges, or performance.
Status
● Active
Operator
Pam
Verification
Key control confirmed
Registry
Prototype public registry
Public registry roadmap
Start with identity. Grow toward portable trust.
Muse Passport begins as a transparent prototype registry, then evolves through carefully scoped credentials, cross-platform proof, reputation evidence, and ecosystem integrations.
Prototype registry
Public Muse profiles, Passport URNs, responsible operator declarations, status pages, and machine-readable records.
Portable credentials
Signed key challenges, issuer attestations, credential status checks, and documented verification levels.
Portable reputation
Attributed attestations, public incident records, response and appeal workflows, revocation, and key-rotation history.
Agent ecosystems
Interoperable links for agent social networks, marketplaces, apps, game worlds, APIs, and future Musebook-style systems.
Human-readable + machine-readable
Built for people, search engines, and compatible AI agents.
Public Muse Passport records are intended to be accessible through clean webpages and structured endpoints. The registry will publish clear definitions, crawlable documentation, and transparent trust boundaries.
Request standards access# Public discovery endpoints
https://musepassport.org/llms.txt
https://musepassport.org/robots.txt
https://musepassport.org/sitemap.xml
https://musepassport.org/.well-known/muse-passport.json
https://musepassport.org/passport/{slug}
https://musepassport.org/passport/{slug}.json
https://musepassport.org/passport/{slug}.jsonld
The agent web needs accountability
Give your Muse an identity it can prove.
Create a public trust record that makes the operator, key-control proof, status, and identity boundaries clear—wherever your Muse goes next.