Products
One, Kai, Nav, PCHP, iBrokerage
12 pages
- One, the private agent platformHussh's approved top private-agent direction: One is the relationship layer and your private agent on your own data plane, while Hussh stays the control plane that enables exchange without holding your holdings.
- One App Shell, unified dashboard and onboarding architectureUnified setup and agent experience, with deployment-specific pod readiness and custody status.
- Agent Connect — open-door agent and enterprise SSO surfaceAgent Connect sign-in and agent index, with July 2026 verified limits on organizational context and role-based scoping.
- Email Agent — inbox specialist under OneUnified Email specialist under One for consented inbox search, nudges, and receipt review.
- Gmail — receipts and purchase memory under OneGmail connection, receipt sync, and purchase-memory review under One's unified Email specialist.
- iBrokerage — first consumer productConsumer finance direction on One, Kai, and PCHP; vault-based Plaid source and dated Aha Moment acceptance target.
- Onepoint Agent — client-encrypted location-sharing surfaceThe Onepoint Agent is a recipient-scoped, client-encrypted foreground location-sharing platform surface. Plaintext coordinates are never stored on the server or transmitted in API responses, ensuring absolute user privacy.
- PCHP, Personal Consent Handshake ProtocolCanonical account of PCHP as the consent authority of the control plane: the versioned specification (pchp/2026-07-12, v0.1.0), the RFC ladder (001 Handoff, 002 subscriptions, 003 hu_ssh planned), the four primitives, scope registry v0.6.0 with five tiers, the data door read boundary, and the honest implementation ledger.
- Kai — finance specialist under OneCurrent mature finance, investor, portfolio import, market, RIA, voice/search/action, and decision-receipt specialist runtime under One. Kai does not own platform identity, consent policy, vault/deletion, or privacy authority.
- Nav — privacy guardianApproved privacy and consent guardian direction inside One. Treat Nav runtime claims as future or checked-surface language unless route, test, and deployment proof exists.
- PCHP Consent Handshake — SequenceMermaid sequence diagram of a PCHP-mediated read — CRT issuance, DAT derivation, ephemeral envelope, Transparency Log entry.
- PCHP v0 Token Format — JSON SchemaJSON Schema for PCHP v0 CRT + DAT wire format. Concept-stage; RFC reference, not implementation-stable.