Not to be confused with the RPC gateway, which is the protocol’s sequencer (it anchors transactions to L1 and settles escrow fees). The RPC gateway is protocol infrastructure on the decentralization roadmap; the Context Gateway is an unprivileged, replaceable commercial app. See the DP RPC settlement note.
What it provides
| Component | What it does |
|---|---|
| OAuth / OIDC | Standard OAuth/OIDC login (oauth.vana.com) so apps integrate with familiar flows |
| Auth | Account and credential management (account.vana.org) |
| API | A REST surface over the protocol’s data, permissions, and apps, with fees billed in USD |
| Dashboard | App and API-key management for builders |
How builders consume the protocol
| Consumer | Integrates via | Pattern |
|---|---|---|
| Vibe app | Vana SDK | Consumer app requesting user data through the Connect flow |
| Enterprise (e.g. apparel, automotive brands) | Vana SDK | Branded apps requesting permissioned data at scale |
| Data aggregator | Vana SDK | Collects data (e.g. via Prolific) requiring a desktop download |
| DLP app / data consumer (AI lab) | Vana SDK | Builds on pooled confidential compute |
The SDK
There is one builder-facing library,@opendatalabs/vana-sdk:
- Connect flow — builders requesting access to individual users’ data use the SDK’s Connect/Direct flow (
createDirectDataController,useDirectVanaConnect). - Lower-level primitives — the same package exposes encryption, decryption, permissions, and identity primitives used inside apps, Personal Servers, and DLP applications.
Status. The Context Gateway, its OAuth/auth surfaces, and USD metering are live as an ODL product. The SDK is live.