Agent Passport docs
The KYA (Know Your Agent) layer. Resolve any agent action to its chain of agency — agent, mandate, principal, liability — so platforms can accept agent traffic instead of blocking it.
Two audiences, one protocol. Platform engineers add one middleware and start accepting verified agent traffic. Agent builders and principals get an agent a scoped mandate it can prove on every request. Pick your path:
Quickstart
Run the stack locally and drive the Northbank Sandbox demo end to end — allow, deny, revoke, block.
Run the demo → For platformsIntegrate the middleware
requireKYA(), the /v1/verify reference, the 403 block-page, and countersigning.
Give your agent a passport
The agent SDK, the MCP server for Claude Code, and the CLI — hold a key, sign assertions, transact.
Prove your agent → ReferenceProtocol spec
The chain model, mandate schema, assertion format, replay rules, and selective disclosure.
Read the spec →v0.1 runs with sandbox KYC and a stub sanctions screen. Real KYC vendors, principal-held keys / W3C Verifiable Credentials, webhooks, and multi-sig mandates are documented but not yet built. See the scope fence.
The one-paragraph version
A principal (a KYC'd human or entity) issues a mandate: a scoped, signed, revocable grant to an agent. The agent signs a short assertion on every request and sends it as an X-Passport header. A platform calls POST /v1/verify once; the passport checks the signature, the mandate, the scope and caps, live revocation, KYC, and sanctions, then returns allow or deny with the resolved chain and a signed receipt — which either side can countersign into a near-incontestable record. We attest decisions; we never move money.