Cowrie Research

octav-primary-sources-2026-04-30

3 min read

Octav primary sources — 2026-04-30

Project status in this pass

  • No canonical standalone whitepaper or litepaper was surfaced during this pass.
  • The clearest current source of truth was the combination of Octav’s homepage, platform docs, API docs, and llms.txt index.

Primary-source snapshots

1) Official homepage

  • URL: https://octav.fi/
  • Key excerpt:
    • The homepage frames Octav Pro as “Portfolio Intelligence for Digital Assets” with automated NAV reports, exposure insights, and exportable snapshots.
    • It claims trust from 200+ digital-asset managers and highlights 2,000,000 tracked tokens, 10,000+ protocols, 1.1B+ indexed transactions, and 100+ API clients.
    • This strongly suggests a reporting and monitoring product for professional operators rather than a narrow consumer dashboard.

2) Platform quickstart

  • URL: https://docs.octav.fi/docs/quickstart
  • Key excerpt:
    • The quickstart says users can add wallet addresses and automatically track supported chains without manual chain selection.
    • It lists major chains such as Ethereum, Base, Arbitrum, Solana, Hyperliquid, BSC, and Polygon, and says the platform supports 90+ blockchains.
    • The page frames Octav as a read-only operational dashboard with widgets, reports, and transaction history rather than as custody software.

3) Reports documentation

  • URL: https://docs.octav.fi/docs/reports
  • Key excerpt:
    • The reports docs expose three distinct report families: portfolio snapshots, transaction reports, and asset-variation reports.
    • Export paths include WEB, PDF, and CSV, and the docs also mention scheduled recurring reports.
    • This is one of the clearest signals that Octav is a reporting control plane and not merely a visual portfolio tracker.

4) API introduction

  • URL: https://docs.octav.fi/api/introduction
  • Key excerpt:
    • The API introduction says integrators can retrieve portfolio balances, transaction history, token analytics, and historical data.
    • It publishes https://api.octav.fi as the base URL, says authentication is via Bearer token, and states a rate limit of 360 requests per minute per API key.
    • The endpoint list covers portfolio, NAV, transactions, token overview, historical portfolio, sync, status, and credits.

5) API quickstart

  • URL: https://docs.octav.fi/api/quickstart
  • Key excerpt:
    • The quickstart walks through credit checks, portfolio queries, and transaction-history calls with cURL, JavaScript, Python, and TypeScript examples.
    • It reinforces that the API is intended as an application-facing integration surface, not just an internal dashboard backend.

6) NAV endpoint docs

  • URL: https://docs.octav.fi/api/endpoints/nav
  • Key excerpt:
    • The NAV docs define a dedicated GET /v1/nav endpoint with a one-credit cost and support for multiple fiat and crypto output currencies.
    • The page also explains 1-minute caching and the waitForSync behavior for fresher reads.
    • This adds weight to the categorization of Octav as an operational monitoring and valuation layer.

7) llms.txt documentation index

  • URL: https://docs.octav.fi/llms.txt
  • Key excerpt:
    • The llms.txt file describes Octav as a read-only, credit-based REST API for real-time multi-chain portfolio data, transaction history, DeFi positions, and historical snapshots.
    • It explicitly includes AI-development guides, an MCP server guide, OpenAPI access, and agent-integration material.
    • That makes Octav notable not just as a reporting platform, but as a docs-first data product that is intentionally agent- and developer-facing.

Working conclusion

Octav is best cataloged as digital-asset portfolio intelligence, NAV-reporting, and analytics-control-plane infrastructure. The strongest evidence is the combination of scheduled and exportable reports, read-only multi-chain portfolio tracking, API-first NAV and historical endpoints, and explicit AI-agent / MCP integration guidance.

Graph View