Read hot context
Ask for a narrow slice the user can understand: writing voice for this draft, dietary constraints for this trip, or active project notes for this session.
For developers
Ask for hot context. Leave a receipt.
Your app or agent asks Passport for the exact fields it needs: preferences, active projects, saved facts, taste, or other hot context. The user approves; your app reads only those fields, can propose durable updates back to the Passport inbox, and every read or write leaves a receipt.
Surface
Permission flow
OAuth tells an app which account it can access. Passport tells an AI app which context it can read or propose back. The pilot surface is intentionally small: one request, one reason, one user decision.
Write to the inbox
When your app learns something durable, propose it to Passport. The user accepts, edits, or rejects it before it sticks.
Keep receipts
Each read or write records app, scope, reason, time, and expiry. Users should not have to guess what your app saw.
For companies
Remember the person, not the case
Some of the earliest interest in Passport comes from companies that work with the same person across many cases and teams. They use Passport the same way apps do, as a per-user memory store, but pointed inward, with memories marked internal to their organization.
Keep context across cases
Cases close, but the person comes back. Passport keeps what your organization has learned about them in one place, so the next case, team, or agent does not start over.
Answer GDPR from one place
Memories live per person, in that person's passport, rather than pooled in a warehouse. Access, erasure, and portability requests point at one store instead of every system you run.
Integrate once
Case systems, support desks, and internal agents read and write one per-user memory API. Mark memories as internal to your organization and Passport stores them with the rest of the person's passport.
Request grammar
Show the user the actual request
Builders should be able to describe the request in a few fields. Users should be able to approve it without guessing what the app will see.
{
"read": ["writing_voice", "active_project"],
"purpose": "draft onboarding email",
"duration": "this session"
}- Your app asks Passport for two named fields.
- The user sees the app, reason, fields, and duration.
- Approval returns a bounded pass for this session.
- The read leaves a receipt the user can inspect later.
Expression of interest
Tell us what you want to build with Passport
Tell us what you are building and how you would want to use Passport. A sentence or two is plenty; we will take it from there.