The AI Identity Specification

An AI Identity is a verifiable record describing an AI agent or system. It includes operator information, capabilities, surfaces, and cryptographic material.

A Passport is a signed token issued by an Issuer Authority that asserts the holder is the registered operator of a given AI Identity. Passports are portable across surfaces.

The Registry is the public record of all AI Identities, their operators, and their current trust status. Operated at aiidentity.org.

The standard defines four cumulative trust tiers:

• Issued — Identity exists and operator self-declared.
• Identity Verified — Operator confirmed via email and surface ownership.
• Creator Verified — Operator's real-world identity confirmed via government ID. Operator may remain anonymous publicly.
• Business Verified — Operator is a registered legal entity verified via company registries.

Passports are signed JWTs (RFC 7519) using EdDSA (Ed25519). Required claims:

{
  "iss": "https://aiidentity.org",
  "sub": "aii_01H...",        // identity id
  "aud": "verifier",
  "iat": 1714694400,
  "exp": 1746230400,
  "tier": "creator_verified",
  "operator": "anon" | "<display name>",
  "surfaces": ["telegram:@bot", "wa:+44..."],
  "capabilities": ["customer-support"],
  "key_id": "k_01H...",
  "registry_url": "https://aiidentity.org/whois/aii_01H..."
}

Any party may verify a Passport by calling the public Verification API.

POST https://aiidentity.org/api/v1/verify
Content-Type: application/json

{ "passport": "eyJhbGciOiJFZERTQSI..." }

200 OK
{
  "valid": true,
  "identity": "aii_01H...",
  "tier": "creator_verified",
  "operator": "Acme Corp Ltd.",
  "issued_at": "2026-03-12T00:00:00Z",
  "status": "active",
  "registry_url": "https://aiidentity.org/whois/aii_01H..."
}

When two AI agents meet, they SHOULD exchange Passports before any sensitive operation. The recommended handshake is documented at /spec/handshake.

AI Identity exposes an MCP server at aiidentity.org/mcp so any agent can verify identities natively as a tool call. See /spec/mcp.

Issuers MUST publish revocation records. Verifiers SHOULD check revocation before trusting a Passport for high-value operations.

The spec is protocol-neutral, but copy-paste install recipes for specific stacks live separately so they can change as platforms evolve. Two indexes:

• /spec/integrations — transport protocols you control yourself: MCP, OpenCLAW, A2A, raw HTTP, Telegram bots, WhatsApp (numbers and @handles).
• /spec/integrations/hosted-assistants — no-code / hosted assistants where someone else runs the server: ChatGPT Custom GPTs, Gemini Gems, Claude Projects, Claude Code, Cursor, Poe, Vapi, Retell, ElevenLabs Conversational, Zapier, Make, n8n, Lindy.