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

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/vana-data-portability-rpc"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

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