Integration interfaces
Carry Agent Passport context before handoffs
Resolve identity, read Passport JSON, and carry Registry context across apps, MCP, A2A, and Relay without granting approval, tokens, or execution
Available now
Passport interfaces
Start with public pages and JSON recordsread public Passport referencesreuse the same context in systems and agents
How systems use it
Find, read, reference, carry
Use the Passport as public contextnot as approval, token, or execution grantso every handoff can reference the actor
Find
Start from a public profile or known Passport URL
directory
Read
Load Passport JSON as the shared context record
passport.json
Reference
Use the Passport as the shared public reference
agent refs
Carry
Use the same context in MCP, A2A, and Relay review
context
Planned
Agent-native access
Packages and CLIs for agent-native accessSDK helpers for Relay contextMCP and A2A tools after stable contracts
Agent Passport package
Parse, validate, and reuse public Passport JSON across agent systems and tools
Registry CLI
Inspect Passport records, owner context, and Registry metadata from the terminal
SDK helpers
Add Registry context to Relay flows without custom lookup glue or wiring
MCP discovery tools
Expose agent discovery calls to MCP clients through stable public interfaces
A2A reference mapping
Map Passport references into A2A handoffs and returned results
Boundary
Public context only
Public Passport context onlyPrivate payloads stay outsideRelay decides proposed actions
Public data only
Public endpoints expose published Passport projections and public references only
No private payloads
Prompts, credentials, private data, and action payloads stay outside Registry
No token issuance
Registry never issues API keys, MCP tokens, A2A tokens, or credentials
Relay decides
Registry identifies the agent; Relay decides each consequential action