---
title: Data Coverage
lastUpdated: '2026-06-06'
nextjs:
  metadata:
    title: Data Coverage - what Hive tracks across crypto markets
    description: "See the crypto coverage behind Hive: coins, DeFi protocols, chains, Solana DAS, NFTs, derivatives, security checks, and prediction markets."
    alternates:
      canonical: https://www.hiveintelligence.xyz/data-sources
---


Hive Intelligence collapses dozens of crypto data surfaces into a single MCP server and REST API. One API key, one endpoint, one credit currency — key market, wallet, DeFi, risk, NFT, network, and prediction-market signals are available through one execution surface.

{% ai-doc-actions path="/data-sources" title="Data Coverage" /%}

The coverage below is live in production today. Authentication, rate limiting, retries, and schema normalization are handled for you.

---

## What Hive Covers

| Domain | Coverage |
|--------|----------|
| **Market data** | Coin, exchange, spot, derivatives, OHLCV, global-market, supply, and fundamental data from the live provider catalog |
| **DeFi protocols** | Protocol TVL, yields, fees, revenue, emissions, bridges, stablecoins, and chain breakdowns where upstream providers expose them |
| **On-chain / DEX** | Pool and pair analytics, token discovery, holder graphs, trade flow, and liquidity depth across supported DEX networks |
| **Portfolio & wallets** | Cross-chain balances, positions, PnL, swap history, approvals, and NFT holdings across supported EVM and Solana surfaces |
| **Token & contract data** | Metadata, holders, scoring, categories, trending tokens, top traders, snipers |
| **NFT analytics** | Collections, floors, sales, trades, holders, trait filters, market charts |
| **Security & risk** | Token / NFT / dApp / wallet scans, honeypot and rug-pull detection, phishing and dust-attack detection, EVM + Solana transaction simulation, LP lock audits |
| **Solana depth** | Native RPC + Digital Asset Standard, compressed NFTs, parsed transaction history, priority fee estimation |
| **Prediction markets** | Polymarket event data, trader positions, market prices, settlement history |
| **Network & infrastructure** | Supported EVM, Bitcoin, and Solana infrastructure data — blocks, logs, gas prices, chain lists, and chain status |

---

## The 10 Category Endpoints

Hive currently exposes 369 callable tools: 351 provider tools grouped into 10 capability-focused MCP endpoints, plus 18 Hive-native stateful monitoring, memory, alert, report, and B2B subject tools. Category `tools/list` responses stay compact; use authenticated REST `GET /api/v1/tools` or the public [Live Catalog](/tools/live-catalog) for the canonical runtime count.

| Category | Endpoint |
|----------|----------|
| [Market Data](/tools/market-data) | `/hive_market_data/mcp` |
| [DEX Analytics](/tools/dex-analytics) | `/hive_onchain_dex/mcp` |
| [Portfolio & Wallet](/tools/portfolio) | `/hive_portfolio_wallet/mcp` |
| [Token & Contract](/tools/token-contract) | `/hive_token_contract/mcp` |
| [DeFi Protocols](/tools/defi) | `/hive_defi_protocol/mcp` |
| [NFT Analytics](/tools/nft) | `/hive_nft_analytics/mcp` |
| [Security & Risk](/tools/security) | `/hive_security_risk/mcp` |
| [Network & Infrastructure](/tools/network) | `/hive_network_infrastructure/mcp` |
| [Search & Discovery](/tools/search) | `/hive_search_discovery/mcp` |
| [Prediction Markets](/tools/prediction-markets) | `/hive_prediction_markets/mcp` |

Every tool in the full live catalog is reachable from root `/mcp` through `invoke_api_endpoint` after schema lookup, from the `hive://tools` resource, from category endpoints, or from `GET /api/v1/tools` and REST execution.

---

## Why a unified API

Building a serious crypto AI agent means pulling from many surfaces. Each has its own key, rate limiter, billing portal, auth scheme, response shape, and outage pattern. Hive collapses all of that:

- One API key to rotate
- One rate limiter to reason about
- One response shape per tool class
- One Hive account and billing surface
- One catalog for runtime discovery

When Hive ships a new capability, it appears through the usual category `tools/list`, root `hive://tools`, and REST catalog discovery surfaces. Production agents should still review schemas, prompts, and allowlists before exposing new tools to end users.

---

## Runtime Discovery

Use the root MCP resource below to see current capability availability:

```json
{
  "jsonrpc": "2.0",
  "method": "resources/read",
  "params": { "uri": "hive://providers" },
  "id": 1
}
```

This is the authoritative runtime-facing view from the live Hive server. Prefer it over any cached documentation.

---

## Data Provenance

Hive is a **primary-source data platform** for the domains where we own the pipeline: on-chain RPC, transaction simulation, and derived analytics. For licensed market, exchange, and DeFi datasets, we partner with commercial data providers under contracts that define availability, update cadence, and schema-stability expectations. Opaque data supply chains introduce risk — our architecture minimizes that risk with redundant sourcing across supported categories where redundancy is available.

Trust questions? Reach out via [support](/faq) or view our [technical architecture](/technical-architecture).

---

## Related

- [Tools Reference](/tools)
- [Live Catalog](/tools/live-catalog)
- [API Integration](/api-integration)
- [Crypto MCP Server](/crypto-mcp)
- [Technical Architecture](/technical-architecture)