Vana website screenshot

Vana

Vana is an open protocol for user-owned, portable personal data — sovereign data infrastructure for the AI economy. Users store personal data in Personal Servers, grant builders access via signed, scope-native EIP-712 permissions, pay protocol fees from an onchain escrow, and revoke access at any time, with all consent recorded on the EVM-compatible Vana L1. Builders integrate through the @opendatalabs/vana-sdk, the Data Portability RPC, a local-first data-collection CLI, and an MCP interface on every Personal Server. Stewarded by the Vana Foundation and developed by Open Data Labs; backed by Paradigm.

Vana publishes 2 APIs on the APIs.io network. Tagged areas include Company, Crypto Ai, Data Portability, Personal Data, and Data Sovereignty.

Vana’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, signup flow, authentication, and 23 more developer resources.

35.5/100 thin ▬ flat Agent 12/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessSelf serve
2 APIs 1 MCP Servers
CompanyCrypto AiData PortabilityPersonal DataData SovereigntyBlockchainWeb3AgentsArtificial Intelligence

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/vana: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

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, s...

Vana L1 JSON-RPC

Standard Ethereum JSON-RPC for the EVM-compatible Vana L1 blockchain, which records registrations, grants, file records, and schemas. Mainnet at rpc.vana.org (explorer vanascan....

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Vana MCP Server

MCP SERVER

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Vana Authentication

web3-signed/eip712-grants/oauth2-oidc · 4 schemes

SECURITY

Vana Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Vana Vulnerability Disclosure

contact published

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: vana
name: Vana
description: Vana is an open protocol for user-owned, portable personal data — sovereign data infrastructure for the AI economy.
  Users store personal data in Personal Servers, grant builders access via signed, scope-native EIP-712 permissions, pay protocol
  fees from an onchain escrow, and revoke access at any time, with all consent recorded on the EVM-compatible Vana L1. Builders
  integrate through the @opendatalabs/vana-sdk, the Data Portability RPC, a local-first data-collection CLI, and an MCP interface
  on every Personal Server. Stewarded by the Vana Foundation and developed by Open Data Labs; backed by Paradigm.
url: https://raw.githubusercontent.com/api-evangelist/vana/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://vana.org/assets/logos/vana-asterisk-data-signal.svg
x-type: company
x-source: vc-portfolio
x-backed-by:
- paradigm
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Crypto Ai
- Data Portability
- Personal Data
- Data Sovereignty
- Blockchain
- Web3
- Agents
- Artificial Intelligence
apis:
- 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
- name: Vana L1 JSON-RPC
  description: Standard Ethereum JSON-RPC for the EVM-compatible Vana L1 blockchain, which records registrations, grants,
    file records, and schemas. Mainnet at rpc.vana.org (explorer vanascan.io); Moksha testnet at rpc.moksha.vana.org (chain
    ID 14800, explorer moksha.vanascan.io, faucet faucet.vana.org).
  humanURL: https://docs.vana.org/network/vana-l1
  baseURL: https://rpc.vana.org
  tags:
  - Blockchain
  - JSON-RPC
  - EVM
  properties:
  - type: Documentation
    url: https://docs.vana.org/network/vana-l1
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.vana.org
- type: DeveloperPortal
  url: https://docs.vana.org
- type: Documentation
  url: https://docs.vana.org
- type: APIReference
  url: https://docs.vana.org/protocol-reference/full-specification
- type: GettingStarted
  url: https://docs.vana.org/build-a-vana-app
- type: Support
  url: https://docs.vana.org/resources/community-discord
- type: Blog
  url: https://vana.org/blog
- type: GitHubOrganization
  url: https://github.com/vana-com
- type: TermsOfService
  url: https://vana.org/terms
- type: PrivacyPolicy
  url: https://vana.org/privacy
- type: SignUp
  url: https://app.vana.org
- type: Whitepaper
  url: https://docs.vana.org/resources/whitepaper
- type: Packages
  url: packages/vana-packages.yml
- type: SDKs
  url: packages/vana-packages.yml
- type: WellKnown
  url: well-known/vana-well-known.yml
- type: MCPServer
  url: mcp/vana-mcp.yml
- type: LLMsTxt
  url: llms/vana-llms.txt
  name: docs.vana.org/llms.txt
- type: LLMsTxt
  url: llms/vana-website-llms.txt
  name: vana.org/llms.txt
- type: Conformance
  url: conformance/vana-conformance.yml
- type: ErrorCatalog
  url: errors/vana-problem-types.yml
- type: Lifecycle
  url: lifecycle/vana-lifecycle.yml
- type: Authentication
  url: authentication/vana-authentication.yml
- type: DomainSecurity
  url: security/vana-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/vana-vulnerability-disclosure.yml
- type: Security
  url: https://docs.vana.org/resources/security
- type: Sandbox
  url: sandbox/vana-sandbox.yml
- type: Conventions
  url: conventions/vana-conventions.yml
- type: CLI
  url: cli/vana-cli.yml
- type: Components
  url: components/vana-components.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 19
  pass: local-v1

Work with this as data

Every provider 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 providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • 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 provider
curl "https://apis.io/api/v1/providers/vana"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/vana/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/vana/evidence"

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.

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