Vana

Vana Data Portability RPC

The protocol's read/write boundary — a caching and relay layer between protocol participants and the Vana L1 covering the onchain primitives (identity, permissions, fees, PGE, schemas, files, DLP contracts) with EIP-712 verification and the L1 settlement path. Builders' requests to users' Personal Servers (REST /v1: data, grants, access logs) are authorized with Web3Signed headers under scope-native grants.

GitHub

Documentation

📖
Documentation
https://docs.vana.org/protocol-reference/dp-rpc
📖
APIReference
https://docs.vana.org/protocol-reference/personal-servers

Other Resources

🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/vana/refs/heads/main/apis.yml

API entry from apis.yml

apis.yml Raw ↑ 
name: Vana Data Portability RPC
description: 'The protocol''s read/write boundary — a caching and relay layer between protocol participants
  and the Vana L1 covering the onchain primitives (identity, permissions, fees, PGE, schemas, files, DLP
  contracts) with EIP-712 verification and the L1 settlement path. Builders'' requests to users'' Personal
  Servers (REST /v1: data, grants, access logs) are authorized with Web3Signed headers under scope-native
  grants.'
humanURL: https://docs.vana.org/protocol-reference/dp-rpc
baseURL: https://dp-rpc.vana.org
tags:
- Data Portability
- Grants
- Permissions
- Escrow
properties:
- type: Documentation
  url: https://docs.vana.org/protocol-reference/dp-rpc
- type: APIReference
  url: https://docs.vana.org/protocol-reference/personal-servers