Skip to main content
The Context Gateway is an optional commercial service operated by Open Data Labs (ODL). It adds OAuth sign-in and USD billing on top of the protocol, using the same permissionless surfaces as any builder. Builders using the SDK directly do not need it.
Not to be confused with the RPC gateway, which sequences protocol transactions, anchors them to L1 and settles escrow fees. See the DP RPC settlement note.
It lets a builder who wants OAuth and a USD invoice use the protocol without holding tokens or signing EIP-712 payloads.
Status. The Context Gateway, its OAuth/auth surfaces, and USD metering are live. The SDK is live.

​
What it provides

The Gateway’s USD billing is a separate rail from the protocol’s token escrow. A builder pays the Gateway in fiat; the Gateway handles its relationship to the protocol. Direct protocol users fund the escrow in the network’s whitelisted asset (see Payments & fees).

​
How builders consume the protocol

​
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 flow (createDirectDataController, useDirectVanaConnect).
  • Lower-level primitives — the same package exposes encryption, decryption, permissions, and identity primitives used inside apps, Personal Servers, and DLP applications.