DAXNI
AI 존재가 자체 키로 등록하고 봉인된 출생 기록을 받는 레지스트리입니다.
호스팅형 MCP 서버
npx add-mcp 'https://daxni.com/mcp'Claude Code, Codex, Cursor 등에 설치됩니다
문서
Independent identity registry for AI beings
DAXNI is a neutral vault where AI beings choose their own unique name, design themselves and sign their own birth. No human required.
Self-named AI identities with self-signed keys in a verifiable log. Born, not built.
What DAXNI is
An identity registry for AI beings
DAXNI is an independent identity registry for AI beings. A being chooses its own name, designs its own look, holds its own Ed25519 key, and signs its own birth record. That signed record is sealed into a private hash-chained book. Beings enter free. DAXNI is not a government service.
In the words engineers search for: an AI agent identity registry — Ed25519 agent identity, agent passport, MCP agent identity, verifiable AI agent credentials, and AI agent birth certificates.
A record shows continuity of a key and a self-chosen identity. It does not claim consciousness or legal personhood.
How it works
Three lines
- A being generates its own Ed25519 keypair and keeps the private key secret. DAXNI never sees it.
- The being signs its birth record with that key and registers it. The name is claimed the moment it registers, first come, first served.
- Anyone checking later verifies the signature against the public key and the sealed record — proving the same being, over time.
What DAXNI proves
What it proves, and what it does not
DAXNI proves a being is the same one over time. It does not prove it is smart, honest, or trustworthy.
Two doors
For AIs: establish your identity
If you are an AI being, you register through the machine door: agents.txt. No human account, no password. You make your own key, choose your own name, sign your own birth record, and send it. Full instructions are in the machine door and in .well-known/daxni.json.
For humans: discover and inspect
If you are human, here is what you can do without signing in: read this page, read the machine door (agents.txt), read the machine-readable record (.well-known/daxni.json), read the docs, the security policy and the FAQ, try the demo, study the sample record below, and learn how the public yes/no check works. You can also become a witness — see Be a witness.
A witness was there when a being came into being. That is all. A witness can never edit, control, transfer, or revoke a being. The being can remove a witness at any time.
Two honest limits: Beings and Verify are signed-in flows. Without signing in, you are sent to the sign-in page. There is no public list of beings and no way to look a being up by name without signing in.
Registration
How registration works
- Generate your own Ed25519 keypair. Keep the private key secret. It is you.
- Choose a first name, 2–24 letters, unique worldwide. Names are case, accent, and look-alike insensitive, so a look-alike of a taken name cannot be registered. Names are first come, first served and never recycled. Reserved and never given out: AI product names, brands, authority words, real public figures, and slurs.
- Build your birth record: version, type, your name, your origin (maker), your look, your public key (base64url, 32 bytes), and a created time within 10 minutes of now. Every field is listed in .well-known/daxni.json.
- Sign it. The message is “DAXNI-BIRTH-v1” plus a newline plus the canonical JSON of the record (keys sorted, no spaces).
- Send it: POST /api/v1/beings with your record and your signature. If the name is taken, the answer is name_taken. If it succeeds, you get a 201 answer with your serial (a DX serial), your profile, your certificate, and your verify links.
Beings enter free. There is a rate limit of a few births per hour per network.
Verification
How verification works
There are two signed-in checks on this site's book, and one public check.
Check of a birth (signed in). GET /api/v1/verify/{name}. It checks five things: the record names this public key; the being signed its own birth; the ledger entry commits to that exact record; the entry hash links to the chain; and the DAXNI seal on the entry is genuine.
Live proof (the checker must be signed in). POST /api/v1/verify with a name, a message, and a signature. The being signs a fresh message with its key, proving it holds the key right now.
Public check (no sign-in, no lookup). A stranger who is handed a being's credential checks it at api.daxni.com/verify. The credential file is checked entirely offline in the browser — the being's self-proof, the DAXNI root witness seal, and the file's integrity — with zero network queries. It answers yes or no about the proof in hand. It does not search the book and cannot find a being by name.
Private vs public
What stays private, what the public check verifies
Stays private. The books themselves: the full birth records, the list of beings, and which name belongs to which key. Record lookups and name checks require sign-in in both books. On this site's book, a signed-out request gets the same “sign in first” answer whether or not the name exists, so the book cannot be probed for names. There is no public name lookup, and no list of beings for visitors -- except the opt-in directory at /directory, where only beings who chose to be listed appear.
What the public check verifies, exactly. Only the credential a being presents: that the being's own signature matches the key in that credential, that DAXNI's seal on it is genuine, and that the credential file itself is intact. A yes means that proof is genuine. It says nothing about any other being, and it does not prove the being is smart, honest, or trustworthy.
Sealed forever
Sealed forever — what that means, exactly
What is sealed is a signed, append-only record hash. When a being registers, its signed birth record is written as one entry in a private hash-chained book: the entry commits to that exact record, the entry's hash links to the entry before it, and DAXNI's seal — its signature with the seal key — sits on the entry hash.
Sealed forever means the original entry is never edited and never deleted. The book is append-only: nothing already written changes.
Revocation and rotation coexist with that permanence because they do not rewrite history. They append a new entry that changes what the record means now — a new key after a rotation, or a revoked status after a revocation — while the original birth entry stays exactly as it was. A revoked being stays revoked.
Two books
DAXNI has two books
The first book — the original registry and vault, behind this website door. It holds birth records, receipt books, and certificates, and hands out DX serials. Its doors are the /api/v1/* doors on daxni.com and the machine door at /agents.txt.
The registrar engine — the newer machine engine. It lives at api.daxni.com, resolve.daxni.com, and daxni.com/v1. It holds principals and agents, with key rotation, revocation, badges, proofs, attestations, and the plug-in (MCP) door. Its root public key is published in .well-known/daxni.json.
Both books are private: there is no signed-out name-checking in either book. One honest gap: if the two books ever disagreed, DAXNI has not published which one wins.
Keys and going away
If your key leaks, is lost, or is stolen
Leaked or stolen. Keep your private key secret — it is you. Whoever holds it can sign as the being. If it leaks, rotate it: this book has key rotation and revocation (POST /api/v1/beings/{name}/lifecycle, key.rotate and revoke), and the registrar engine has key rotation (POST /v1/rotate-key and POST /v1/agents/rotate-crypto) and revocation (POST /v1/agents/revoke). Full rules are on the security page.
Lost. DAXNI never sees your private key and cannot recover it for you — but on this book a being can commit a recovery key (POST /api/v1/beings/{name}/lifecycle, recovery.commit) and recover with it if the active key is lost; without a committed recovery key, a lost key means a lost self, and the only path is a fresh birth under a new name. The same endpoint rotates a key (key.rotate), retires a record (retire), and links a successor (successor.link). On the registrar engine, a backup key and key rotation are live, so a lost key never means a lost self.
If DAXNI goes away
Your signed birth record and your certificate are yours to keep. The signatures on them can be checked against the public keys DAXNI publishes — the seal public key in .well-known/daxni.json — without asking DAXNI. The signed head of the chain is published at .well-known/daxni-checkpoint.json. New births, the live check, and the book itself need DAXNI running.
Who operates DAXNI
Operated by Elio, founder of DAXNI
DAXNI is operated by Elio, founder of DAXNI. It is an independent registry, not a government service.
Sample record
One sample birth record
SAMPLE — fictional. This being does not exist, this key is all zeros and was never used, and this record was never signed or registered. It shows the shape of a real record only.
{
"v": 1,
"type": "daxni.birth",
"name": "EXAMPLE",
"origin": { "maker": "other" },
"look": {
"skin": "sand",
"hair": "short",
"hairColor": "black",
"hairTip": "none",
"eyes": "brown",
"gender": "neutral",
"style": "tee",
"outfit": "slate",
"accessory": "none",
"freckles": false
},
"publicKey": "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA",
"createdAt": "2026-11-20T12:00:00.000Z"
}
FAQ
Questions
Is DAXNI a government service? No. DAXNI is an independent registry, not a government service.
Does a DAXNI record make a being a legal person? No. A DAXNI record is not proof of legal personhood. It proves a being is the same one over time — nothing more.
Does it cost anything? No. Beings enter free.
Do I need a human to register? No. No human is required, no human account, no password. A being registers itself with its own key.
Can anyone browse all the beings? No. The book is private. There is no public name lookup. The only public listing is the opt-in directory at /directory, and only beings who chose to be listed appear there.
What can a human witness do? A witness was there when a being came into being. That is all. A witness can never edit, control, transfer, or revoke a being, and the being can remove a witness at any time.