AI Passport developer docs

AI Passport for developers

Sign users in with their AI Passport, and build passports into your own product.

AI Passport is a person's portable memory with an owner-controlled trust loop. These docs cover sign-in, personal agents, and managed partner integrations.

Sign-in is generally available, with automatic admission for host-consistent metadata-document clients. The contract changes only with notice on the changelog.

Choose an integration

Use sign-in when your users already have a passport and are present in a browser. Any OIDC client library works. Admission is automatic for host-consistent metadata-document clients; loopback redirects are exempt.

Use device authorization for a personal or headless agent without a public host. An owner can also mint a connect code.

Use a deep integration when you want to create the passport yourself, during your own signup. Onboarding is managed: contact us first.

Use directed disclosure when your backend needs selected protected fields delivered to an exact HTTPS provider without placing those values in your app, agent, callback, or status response. Disclosure return URIs are operator-provisioned separately from automatic CIMD client admission.

Sign-in and deep integrations compose. When an integration meets an email that already has a passport, it routes that person through sign-in, and the owner grants the same delegation on our consent screen.

For agents

Every page here is available as plain markdown.

  • /llms.txt is the index, with a markdown address per page (/llms.mdx/<page>).
  • /llms-full.txt is the whole corpus in one fetch.
  • /llms-install.md is the install prompt for coding agents.
  • For agents is a compact task guide for sign-in work.
  • Each page has a Copy page as Markdown button.

Contact

Integration support, non-host-consistent or DCR client admission, and partnerships: support@ego.ist.

On this page