Octav
Octav is a cryptocurrency portfolio intelligence platform that provides real-time, multi-chain portfolio data, transaction history, DeFi protocol positions, and historical snapshots across 65+ blockchain networks and 2M+ tokens. Its credit-based, read-only REST API lets developers and AI agents build portfolio dashboards, tax tools, NAV reporting, alerting, and analytics applications, with decoded DeFi positions (lending, LPs, staking, vaults, perps), Solana and EVM address support, Ethereum Beacon validator data, and drop-in migration guides from DeBank, Zerion, Zapper, Nansen, Covalent, and others. Octav is SOC 2 Type 1 & 2 certified and ships official MCP server, Rust CLI, and Agent Skill tooling. Backed by Speedinvest.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Octav the way a machine reads it — 18 machine-readable artifacts across 14 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Octav scores 54.4/100 (developing), with a separate agent-readiness read of 69/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Octav
Each block below is one kind of artifact we hold for Octav. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 14
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Octav Airdrops API
Airdrop eligibility endpoints
Octav Approvals API
Token approval endpoints
Octav Beacon Validators API
Ethereum beacon chain validator endpoints — details, rewards, withdrawals, and deposits (mainnet only)
Octav Chains API
Blockchain network and protocol endpoints
Octav Contract Protocol API
Resolve a contract address to its DeFi protocol
Octav Credits API
Credit balance endpoints
Octav Nav API
Net Asset Value endpoints
Octav Portfolio API
Portfolio and holdings endpoints
Octav Status API
Status check endpoints
Octav Sync API
Data synchronization endpoints
Octav Tokens API
Token data endpoints
Octav Transactions API
Transaction history endpoints
Octav Virtual Users API
Virtual user management and portfolio endpoints (Pro only)
Octav Wallet API
Wallet information endpoints
Scroll within the panel for all 14 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
octav-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Octav — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 3
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 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/octav · machine-readable index on apis.io