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 is listed with 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.

🌐 Visit website 📡 Profile data on GitHub

37.0/100 thin ▬ flat Agent 12/100 agent aware Front door AI 4/6 moderate Heartbeat 97/100 alive saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 APIs 1 MCP Servers 3 Agent Skills

CompanyCrypto AiData Portability Personal Data Data Sovereignty Blockchain Web3 Agents Artificial Intelligence

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 37.0/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 14.6 / 17

Access Clarity 5.8 / 17

Operational Transparency 1.5 / 11

Contract Governance 1.9 / 10

Discoverability 6.1 / 9

Regulatory Posture 4.2 / 15

Agent readiness — 12/100 · agent aware

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

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.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/vana/"><img src="https://apis.io/badge/vana/card.svg" alt="Vana on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 34.2 — up to +13.2 composite points
Operational Transparency scores 13.2 — up to +11.3 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/vana/apis.yml: open an issue on github.com/api-evangelist/vana to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Agent Skills (SKILL.md packages)	standard	17.2 (thin)	-	1
LF Decentralized Trust (Hyperledger) Members and Projects (enterprise blockchain, digital identity, CBDC)	standard	17.2 (thin)	-	1

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

The Ethereum JSON-RPC Interface

prose — states compatibility; nothing published to check it against

22 core of 78 operations graded · api-commons/blockchain

Model Context Protocol (MCP)

measured — observed by APIs.io (documented)

Agent Skills

measured — observed by APIs.io (published)

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

Remote MCP server over HTTP.

MCP SERVER

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

connect-data

AGENT SKILL

create-connector

AGENT SKILL

next-prompt

AGENT SKILL

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

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

WellKnown

MCPServer

LLMsTxt

LLMsTxt

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

Components

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

SDKs

CLI

Access & Security 4

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Whitepaper

Whitepaper

Source (apis.yml)

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: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  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'
x-docs-platform: mintlify
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-17
x-docs-hosting: vercel
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

Vana API — frequently asked questions

Does Vana have an API?

Yes. APIs.io lists 2 APIs from Vana, including Vana Data Portability RPC and Vana L1 JSON-RPC.

How do I authenticate with the Vana API?

Vana uses bearer-token authentication (web3-signed/eip712-grants/oauth2-oidc · 4 schemes). The details are profiled on APIs.io as Vana Authentication.

Does Vana have an MCP server?

Yes. APIs.io lists 1 MCP server for Vana: Remote MCP server over HTTP.

Is the Vana API ready for AI agents?

Vana has a Kin Score of 37.0 out of 100 (thin) and an Agent Readiness score of 12.4 (agent-aware), scored by API Evangelist on 2026-11-06.

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"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.