Supported Chains
Supported blockchain networks, chain IDs, URL structures, and feature availability.
BlockVectra is a multi-chain blockchain data provider. With a single API key, you can call JSON-RPC and the Data API on every chain we support through one unified gateway.
One key, all chains
- Universal key: the same API key works on every blockchain network BlockVectra supports — no separate keys per chain.
- Chain in the URL (Data API): each Data API request names its chain explicitly through the
{chain}path segment. - Aggregated usage: account balance, Compute Unit (CU) rate-limit buckets, and free-tier per-second request limits are shared across all chains.
- Plan-based pricing: the exact prices and limits come from your active plan configuration. See Pricing.
URL templates
Standard URL structures for calling JSON-RPC and the Data API:
| Service | Mode | URL template | Notes |
|---|---|---|---|
| JSON-RPC | Key in the path | POST /v1/{api_key} | Simplest form; recommended for curl and HTTP clients |
| JSON-RPC | Key in a header | POST /v1/ | Pass the key in the x-api-key: {api_key} request header; note the trailing slash |
| Data API | REST endpoints | GET /v1/data/{chain}/… | Pass the key in the x-api-key request header |
| Status | Public status | GET /v1/status | No key required; returns each public chain's status and head |
Supported chains matrix
The blockchain networks currently available on BlockVectra, with their service capabilities:
| Chain | {chain} | Chain ID | JSON-RPC | Data API | Chain-Specific Data |
|---|---|---|---|---|---|
| Robinhood Chain | robinhood_mainnet | 4663 | Live, debug_trace* | Live | Traces (coverage gaps), DEX, Tokenized stocks |
Need another chain? Tell us →
Robinhood Chain
Robinhood Chain is the first blockchain network live on BlockVectra.
- Chain ID:
4663 - Chain name (
{chain}in URLs):robinhood_mainnet - JSON-RPC: standard EVM methods plus
debug_trace*execution tracing. - Data API datasets: blocks, transactions, ERC-20 transfers and balances, NFTs, DEX trades and prices, and tokenized stocks.
- Trace coverage: coverage has gaps. Ranges outside the traced window are recorded in
_trace_gaps, and the Data API returns422 no_coverage(not billed) for requests outside coverage. - L2-specific fields: blocks and transactions include L2-specific fields.
Discovering chains programmatically
Use these public endpoints to discover supported chains and their status:
1. Gateway status (GET /v1/status)
A public endpoint that requires no API key (CORS *). It lists only publicly available chains and returns their status and indexed head:
curl -s "https://dev-api.blockvectra.network/v1/status"Example response:
{
"checked_at": "2026-09-28T07:40:00Z",
"gateway": { "status": "ok" },
"chains": [
{
"chain": "robinhood_mainnet",
"chain_id": 4663,
"head": {
"block": 74600000,
"time": "2026-09-28T07:39:58Z",
"lag_seconds": 3
}
}
]
}If a chain is syncing, calls to that chain return -32010; other chains are unaffected.
2. Data API chains (GET /v1/data/chains)
Requires an API key in the x-api-key header (billed at 1 CU). Returns the chains the Data API has indexed:
curl -s "https://dev-api.blockvectra.network/v1/data/chains" \
-H "x-api-key: $BLOCKVECTRA_API_KEY"Example response:
{
"data": [
{
"chain": "robinhood_mainnet",
"chain_id": 4663
}
]
}