How it works
Every app and AI is racing to know you. This prototype turns that around: there is one place for your self, Enkara; you hold the seal, and the apps you choose reach it through doorways you control.
What’s real here
- Your seal (a passkey) is the only key. You consent once, then only at big moments, like connecting a new app.
- Apps connect with OAuth 2.1 and PKCE. Assistants can register themselves (dynamic registration, or a client ID metadata document), and the MCP server advertises its authorization server through protected-resource metadata.
- Each app gets scopes per side of you: it may read some sides and offer to others, for a purpose it states.
- Apps offer; they never write. A tide decides how each offer fits what’s held: new, the same, an update, or a “still true?” question for you.
- Health & care is sealed: held for you, never on a standing grant. A hard moment is held there with its context; the specific method or means is kept out for now.
- Every read, offer and refusal lands on a hash-chained ledger, and your statement shows it in plain words.
- Your own AI connects over MCP at
https://enkara.me/mcp, using the 2026-07-28 revision with a fallback for older clients.
What’s not real yet
- The person, Maya, is invented.
- The Anren and Serai you see are stand-ins that speak the same protocol the real apps will.
- Custody is trusted: the people running this could read it. The path is the tide running sealed, with keys that come from your seal, so no one running the service can read you.
- Membership and ownership, a cooperative the members govern, is designed, not built.