DEVELOPER DOCUMENTATION
Your first real boundary.
Sign up, review five cultural identities, create a private Passport and issue a scoped credential. Then evaluate a candidate through one of the shared protocols.
REST quickstart ↗
Keep the credential on your server. Begin with a Passport read, then evaluate one candidate under an explicit action ceiling.
Remote MCP ↗
Use the stable HTTPS endpoint and OAuth discovery. Account linking is separate from directory approval.
A2A ↗
The public card describes a synchronous JSON-RPC binding and an opt-in authority lifecycle extension.
OAuth and credential lifecycle ↗
User account sessions, developer keys and assistant OAuth grants have distinct lifecycles and audiences.
Leases and portable proofs ↗
A signed assertion is evidence to inspect, not a universal grant of permission.
TypeScript SDK ↗
The existing thin client shares the REST wire contract and typed errors. Source availability and registry publication are separate states.
Events and audit history ↗
Authority history is captured for inspection. An outbound webhook delivery service is not currently offered.
Error catalog ↗
Stable codes, status and retry semantics.
The action ladder
SUGGEST → RANK → SHORTLIST → ADD_TO_DRAFT → PRESENT_AS_SELECTED. An agent requesting a rung above its allowed ceiling gets ASK; strong affinity cannot expand that ceiling.