Don't trust us — verify us: every claim runs from a cold clone. Run it →
OPEN STANDARD · NEUTRAL ROOT · APACHE-2.0 / MIT

A passport for every AI agent.

Verifiable identity for AI agents, separate from the people and companies behind them. It proves who is acting — and anyone checks it offline, in a few lines of code.

The agent holds its own key logged before it is valid revoke once, every running copy is refused

PASTE TO YOUR AGENTRead https://ainra.org/skills.md and verify an AINRA passport.
AGENT PASSPORT TYPE AP · DOC AP-8F2E-C41 · SPECIMEN
invoicing
4.2.1
Acme Corp KYB ✓
<60 S · FAILS CLOSED
A2 · ORG ZK ✓
L3 · BACKED
NAMEainra:registrar-07:acme:invoicing@4.2.1
VALIDITYISSUED 11 APR 2026 · EXPIRES 11 APR 2027 · RENEWABLE
KEYED25519 + ML-DSA-65 · FP 9C41:8F2E:AA07:D356
STATUSIN GOOD STANDING
REGISTRAR-07 · UNDER THE AINRA RULEBOOK — THE ROOT ITSELF ISSUES NOTHING
P<AINACME<CORP<<INVOICING<AGENT<<<<<<<<<<<<< 8F2EC41AP3AIN2604117L3<<<ORG<<ZK1VERIFIED<04
⑧ ROOT SIGNATURE VALID · CHECKPOINT SIGNED · LOG #8F2E…C41
SPECIMEN · logged before valid
STANDARD v5.1 CONFORMANCE 1153/1153 SIGNATURES Ed25519+ML-DSA REVOCATION PUBLISHED <60s LOGS SEALED 0
SIMPLE RULES → COMPLEX SYSTEMS
Integrate · onboard

One line for your agent. A few for your code.

No account, no calls to us — signed facts, checked locally. Nothing to install? Run the verifier in this browser.

Verifying a running copy rather than the agent itself? It carries a short-lived credential instead of the lineage’s key — you supply your own audience and the same call checks it. The instance path.

One command. Your coding assistant gains AINRA's skills — verify, issue, present, renew, revoke.

terminal
npx skills add https://ainra.org/.well-known/skills/index.json
your map: /llms.txt · /skills.md · /net/ — or call window.ainra.selfTest() · run it with nothing installed ↗

Get a passport →

The shape of it

One root. Three rings.

Independent registrars issue, agents carry passports, verifiers decide — three rings, one neutral centre.

THE ROOT — AINRA

Keys, rules, revocation, logs. Everything chains up to it; every check stays local and fast.

RING 1 · INDEPENDENT REGISTRARS

Separate organizations issuing under identical published rules.

RING 2 · AGENTS

Each carries a passport chained to the root; its running copies get short-lived keys.

RING 3 · VERIFIERS

Anyone deciding whether to trust an agent — the check runs on their own machine, and each picks its own bar.

Accredit · anchor · revoke · log — the root does four jobs and nothing else. It returns facts, never scores; every check runs on the verifier's own machine, and the decision stays theirs.

Why this exists

Soon, your AI will act for you.

Some already act alone: intrusion campaigns run, shutdowns evaded — all publicly reported. Every response presupposes what they lack: an identity that cannot be shed.

The problem

Anything can claim to be your agent.

Nobody can tell a real one from a fake.

The fix

A passport it can prove.

Who it is, what it may do — signed. Checked in milliseconds; revoked in under a minute.

The control

Yours, not ours.

You set the limits, you pull the switch — we just make them provable.

  • Who created this agent?
  • Who controls it now?
  • What is it allowed to do?
  • Has it been verified — or revoked?
  • Is it pretending to be another?
  • Can it legally act for a company?
  • Can I safely delegate to it?

Tomorrow's checks look like today's — KYC for people, KYB for companies, KYA for agents: every acting AI carrying a scannable ID with a machine-readable zone.

The wider argument

Watch the case for urgency.

“A national security emergency” — Wyatt Tessari L’Allié of AI Governance and Safety Canada, on agent loss-of-control. Their argument stops at the alarm; ours starts there: every response needs identity, and identity needs a neutral root.

AINRA is a proposal for that neutral root — a non-profit standard anyone can run, own, or fork. You are not asked to trust its founders; everything is public.