Reference implementation

The reference identity

The canonical demo identity is aii_demo. It exposes every public surface of the spec: a verifiable Passport, a DID document, a WHOIS record, and a .well-known/ai-identity.json for the MCP Identity contract. The identity is flagged is_demoin the registry and is clearly marked as a demonstration record so it can't be confused with a real organisation's Passport.

Try every surface

curl https://aiidentity.org/api/v1/verify -d '{"id":"aii_demo"}'

curl https://aiidentity.org/api/v1/did/did:aiidentity:demo

curl https://aiidentity.org/api/v1/whois/aii_demo

curl https://aiidentity.org/.well-known/ai-identity.json

Use this in your code

The reference identity is permanent and deliberately stable. You can hard-code its ID in fixture data, use it for integration tests, or include it in documentation examples. We will not delete or repurpose aii_demo.

// Node / browser / Deno / Workers — same one-liner
import { verify } from "@aiidentity/sdk";

const result = await verify({ id: "aii_demo" });
if (result.valid) {
  console.log(result.tier);   // "creator_verified"
  console.log(result.score);  // numeric Trust Score
}

What it doesn't do

• It is not a real organisation. Don't use it for actual production verification.
• It is not a key escrow service. Treat the reference Passport as inert demo data only.
• Its Trust Score reflects only its tier + age + (low) Verify volume; it is illustrative, not aspirational.