AI Passport — Open Specification
Goal: Any product can say “We support AI Passport.”
This page is the public entry point for implementers. The canonical machine-readable schema lives in the repository; this document links the pieces together.
Specification documents
| Document | Purpose |
|---|---|
| Technical Specification (SPEC.md) | Document model, file layout, security, grants |
| JSON Schema | Canonical passport structure (validate with Ajv) |
| Example passport | Reference instance |
| API Contract | CLI, SDK, MCP integration surface |
| SDK Reference | Passport.load() programmatic API |
| Security Model | Encryption, key storage, threat model |
| Architecture | Core vs integrations vs plugins |
| Compatibility Checklist | “Supports AI Passport” criteria |
| RFC Process | How to propose schema or API changes |
Versioning
| Layer | Current | Location |
|---|---|---|
| Passport envelope | 1.0.0 |
passport.meta.json, schema |
| npm package | See releases | @ai-passport-core/cli |
| MCP server | 1.0.0 |
MCP version field |
Breaking changes to the passport schema require a major envelope version bump and an RFC.
Integration surfaces
Implementers may integrate via:
- Passport Context JSON — filtered export after grant (recommended for AI consumers)
- MCP tools — stdio server (
ai-passport mcp serve) - SDK —
import { Passport } from '@ai-passport-core/cli/sdk' - CLI — shell scripts and onboarding (
ai-passport onboard)
Consumers must never read ~/.ai-passport/passport.json directly.
Quick compatibility statement
“[Product] supports AI Passport v1.0.0. Users can grant scoped read access to identity, coding, and project sections via the standard grant flow.”
See COMPATIBILITY.md for the full checklist.
Public spec site (future)
Phase 4 MVP ships specification as markdown in this repository. A hosted docs site (GitHub Pages or dedicated domain) will mirror these files — same content, better discoverability.
Track progress in ROADMAP.md.