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 the two ways your product can work with it.
Sign in with AI Passport
Standard OpenID Connect. Your app signs users in the way it would with Google or Apple, and can read their approved memory with the same token.
Drop-in button and SDK
Add the official sign-in control and server-side OpenID Connect helper with
the ai-passport-signin package.
Directed disclosure
Let an owner approve one protected delivery to an exact destination, then return a content-free status to your app.
Deep integrations
A managed, server-to-server API. Create passports inside your own signup flow, link data sources from your UI, contribute memories as an attributed source, and read them back under the owner's passes.
Which one do you need
Use sign-in when your users already have a passport and are present in a browser. Any OIDC client library works. Registration is open.
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. Client admission is managed.
The two compose. When a deep 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.txtis the index, with a markdown address per page (/llms.mdx/<page>)./llms-full.txtis the whole corpus in one fetch./llms-install.mdis 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
Questions, redirect hosts to admit, or a partnership conversation: support@ego.ist.