Protocol v1.1.1 · Locked · MIT
Identity Infrastructure for Production AI Agents
A permanent, portable, independently verifiable identity for every AI agent — who it is, who is accountable for it, what it declares, and what has actually been verified.
Paste any agenid:<ULID> to open its verification card. Programs get JSON from the same URL.
Portable Identity
Every agent gets an agenid:<ULID> that never changes — not when it moves platforms, not when its config changes, not when a deployment is retired. Revoked identities stay on record forever.
Cryptographic Proofs
Operator manifests and authority assertions are bound by pure Ed25519 signatures over RFC 8785 canonical bytes. Anyone can re-verify offline, without trusting AgenID's database.
Machine-to-Machine
The same URL answers a browser with a verification card and a program with the canonical JSON envelope. An agent can ask another agent who it is — and check the signed answer before it transacts.
Three commands to a verifiable agent.
@agenid/core gives you identifiers, RFC 8785 canonicalization, the normative schemas, and the Ed25519 proof engine — the same code that passes the specification's deterministic test vectors byte-for-byte.
<script src="https://agenid.com/badge.js" data-agent="agenid:01J8Z3K3F2QZ9X6V7R4T8N2W5Y"></script>Renders the current verification level, live — a suspended or revoked identity changes everywhere it's embedded.
$ ▍
The operator asserts it. Signed, but not checked. Every manifest starts here.
An independent authority checked a specific claim against specific evidence, and signed that — bound to the exact manifest version.
What the operator explicitly permits the agent to do. Reserved for v1.2 — never inferred from platform configuration.
None of these three states is ever inferred from another. That rule is enforced by key role at verification time, not by convention.