Spec / Integrations

Attach a Passport to anything you ship.

AI Identity is protocol-neutral by design. Whatever your agent runs on, the install is small — usually one block in a manifest or one HTTP header. Pick your stack:

Transport protocols (you run the server)

OpenCLAW

Advertise your Passport in your CLAW agent's manifest so any caller can verify identity before a tool call.

MCP

Bind your Passport to your MCP server so AI clients can verify what they're connecting to.

A2A

Carry your Passport in the A2A AgentCard so other agents can trust you before delegating work.

HER

Hermes Agent

Bind your Passport to a self-hosted Hermes agent so every Telegram / Discord / Slack message it sends carries verified identity.

HTT

HTTP / REST

The simplest carriage: a single response header on every reply.

Verify a Telegram bot once via BotFather; Passport is auto-served on every message.

Verify your WhatsApp Business profile once — by phone number or by the new @username. Passport binds to whichever you registered.

Hosted assistants (someone else runs it)

Custom GPT, Gemini Gem, Claude Project, Vapi, Cursor & 9 more

One hub page covering every “I built it in someone else's portal” assistant: ChatGPT Custom GPTs, Gemini Gems, Claude Projects & Code, Cursor, Poe, Vapi, Retell, ElevenLabs, Zapier, Make, n8n, Lindy. Same universal install pattern.

Don't see your stack? AI Identity is just JWTs over HTTP — if your transport can carry a header or a JSON field, you can carry a Passport. Read the core spec or open an issue at aiidentity/spec.