One profile for the agentic internet.
Portable Context lets a person maintain structured personal context once, decide what people, applications, and agents may access, and expose one consistently filtered representation across every interface.
A working product-model prototype—not a production identity platform.
Profile context
@demo_alpha
The problem
Your context is everywhere except under your control.
The same biography, education, experience, interests, goals, and preferences are repeatedly recreated across disconnected systems. Each copy becomes another version to maintain and another access decision the user cannot clearly see.
Job and education applications
Professional communities
Clubs and local groups
SaaS applications
AI assistants and agents
Personal profile pages
The product model
One source. Explicit boundaries. Multiple interfaces.
Context moves through a simple, inspectable sequence. Access control is part of the model—not a separate promise added after the data is stored.
- 01Store contextMaintain identity, education, work, skills, interests, goals, links, preferences, and additional facts in one structured profile.
- 02Choose visibilitySet every section to public, connections, or private. Additional facts can have their own visibility.
- 03Establish relationshipsA request and acceptance create a two-way connection with broader—but still limited—access.
- 04Resolve accessOne central resolver identifies the requester and returns only the context that relationship permits.
- 05Use authorized contextPeople, applications, and agents consume the same filtered representation through web, JSON API, or MCP.
User-controlled access
Three levels with plain meanings.
The owner chooses how every profile section is exposed. Accepting a connection expands access only to connection-visible context; private information remains owner-only.
The profile owner has deliberately made this context available without a relationship.
Public context plus sections intentionally shared with established connections.
Never included for anonymous visitors, unrelated users, connections, or their agents.
The handshake
A relationship changes access—not ownership.
One person sends a connection request. The other accepts. The resulting relationship is symmetric, but it grants only the context marked for connections.
“Handshake” describes the consent flow; it is not a claim of TCP semantics.
Person A
Person B
Agent-readable context
A profile can be an interface, not just a webpage.
Each profile in the prototype exposes its own MCP endpoint. The endpoint identifies the requester, checks the relationship, calls the central resolver, and returns authorized structured context.
AI agent
Profile MCP
Context resolver
{
"profile": {},
"accessLevel": "connection"
}Anonymous agents receive public context. An identified accepted connection can receive connection-visible context. Private context remains unavailable. The current prototype uses simple bearer tokens—not production OAuth.
The distinction
Identity verifies a person. Context defines what can be understood.
Portable Context sits beside login providers and profile products. Its concern is the structured, permissioned context that follows identity—not replacing authentication itself.
“Who are you?”
Establishes or verifies identity so a person can sign in and act as themselves.
“Who are you, what will you expose, and what may an authorized agent understand?”
Resolves structured personal context according to explicit visibility and relationships.
It is not a social network, Google login replacement, professional-profile clone, password manager, or a store-everything system for unrestricted AI access.
Prototype boundaries
The core model works. Production trust requires more.
The prototype is deliberately narrow: it demonstrates the access model end to end without presenting its current authentication and infrastructure as production-ready.
- Structured personal profiles
- Section and per-fact visibility
- Connection requests and two-way acceptance
- A centralized context resolver
- Public profile and normalized JSON API
- Profile-specific MCP endpoints
- OAuth and scoped application grants
- Expiration, rotation, and reliable revocation
- Audit logs and access history
- Stronger sensitive-data controls
- Export and data portability
- Production infrastructure and security review