Robinhood Chain: JSON-RPC and Data API endpoints

Connect to Robinhood Chain mainnet via BlockVectra JSON-RPC and Data API: chain ID, endpoints, curl examples, method policy, and tokenized stock data.

BlockVectra provides JSON-RPC and Data API access for Robinhood Chain mainnet through a single unified API endpoint.

Network information and endpoints

Every request to Robinhood Chain identifies its target network explicitly in the URL path using the slug robinhood_mainnet. JSON-RPC supports both path-based key authentication and request header authentication (x-api-key), while the Data API serves REST endpoints under /v1/data/robinhood_mainnet/.

The parameters and endpoints below reflect active network parameters:

Parameter / Endpoint	Value / Template	Authentication
Chain ID (EIP-155)	`4663`	Unauthenticated (public)
JSON-RPC (path key)	`POST https://api.blockvectra.com/v1/robinhood_mainnet/{api_key}`	API key in URL path
JSON-RPC (header key)	`POST https://api.blockvectra.com/v1/robinhood_mainnet`	Header x-api-key: {api_key}
Data API base	`GET https://api.blockvectra.com/v1/data/robinhood_mainnet/…`	Header x-api-key: {api_key}
Public status	`GET https://api.blockvectra.com/v1/status`	Unauthenticated (public)

Direct curl examples

You can make JSON-RPC calls immediately using standard HTTP clients. Replace {api_key} with your BlockVectra API key:

Query the EIP-155 chain ID using the x-api-key request header:

curl -s "https://api.blockvectra.com/v1/robinhood_mainnet" \
  -H "Content-Type: application/json" \
  -H "x-api-key: {api_key}" \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

Response structure

Responses adhere strictly to the JSON-RPC 2.0 specification:

Success: Returns an envelope with jsonrpc: "2.0", the matching integer id, and a result string containing the hexadecimal-encoded quantity (eth_chainId returns the hex-encoded chain ID; eth_blockNumber returns the latest block height).
Disallowed methods: Requesting a method outside the network's allowed methods returns JSON-RPC error code -32601 (method not available, not billed).
Out-of-window queries: Historical state requests earlier than the state retention window return JSON-RPC error code -32011 (not billed).
Invalid parameters: Malformed or unallowed request parameters return JSON-RPC error code -32602 (not billed).

Capability and method policy

Available JSON-RPC methods, log block range limits, and historical state retention on Robinhood Chain are published dynamically via GET /v1/chains. Execution tracing (debug_trace*, including debug_traceTransaction) is governed by the chain's method policy:

Network parameters and limits

eth_getLogs block range: Max 1000 blocks per request
Historical state window: Recent 900 blocks (queries beyond return -32011)
Execution tracing (debug_trace*): Supported (debug_traceTransaction, debug_traceCall, debug_traceBlockByNumber, debug_traceBlockByHash)

Allowed methods (methods.allow)

eth_blockNumber
eth_chainId
eth_gasPrice
eth_maxPriorityFeePerGas
eth_blobBaseFee
eth_feeHistory
eth_syncing
eth_getBalance
eth_getCode
eth_getStorageAt
eth_getTransactionCount
eth_call
eth_estimateGas
eth_createAccessList
eth_getProof
eth_simulateV1
eth_getBlockByNumber
eth_getBlockByHash
eth_getBlockReceipts
eth_getBlockTransactionCountByNumber
eth_getBlockTransactionCountByHash
eth_getTransactionByHash
eth_getTransactionReceipt
eth_getTransactionByBlockNumberAndIndex
eth_getTransactionByBlockHashAndIndex
eth_getRawTransactionByHash
eth_getRawTransactionByBlockHashAndIndex
eth_getRawTransactionByBlockNumberAndIndex
eth_getLogs
eth_getUncleCountByBlockNumber
eth_getUncleCountByBlockHash
eth_getUncleByBlockNumberAndIndex
eth_getUncleByBlockHashAndIndex
eth_getHeaderByNumber
eth_getHeaderByHash
eth_sendRawTransaction
net_version
web3_clientVersion
web3_sha3
debug_traceTransaction
debug_traceCall
debug_traceBlockByNumber
debug_traceBlockByHash

Blocked methods (methods.deny)

eth_newFilter
eth_newBlockFilter
eth_newPendingTransactionFilter
eth_getFilterLogs
eth_getFilterChanges
eth_uninstallFilter
eth_subscribe
eth_unsubscribe

Tokenized stock data

On Robinhood Chain, the BlockVectra Data API provides daily on-chain metrics and metadata for tokenized stocks across two endpoints defined in the specification:

Daily leaderboard (GET /v1/data/robinhood_mainnet/stocks): Daily activity leaderboard of tokenized stocks for a specified UTC date, ordered by transfer activity descending.
Get one tokenized stock (GET /v1/data/robinhood_mainnet/stocks/{token}): Token contract metadata and up to 30 days of recent daily metrics by token address.

For detailed request parameters, response envelopes (StockDailyListEnvelope and StockTokenEnvelope), pagination notes, and CU consumption estimates, see the Tokenized stocks guide.

Getting started and API keys

New accounts get 30,000,000 CU on sign-up — no credit card.

Web console: Sign up via Ethereum wallet signature or email, and generate an API key in the Console. See the Quickstart guide for setup details.
Programmatic sign-up: Autonomous AI agents, automated scripts, and CI pipelines can sign in and provision API keys using Ethereum wallet signatures (EIP-191) without a browser. Follow the Programmatic sign-up guide.
AI agents: Autonomous AI agents can discover Robinhood Chain capabilities and create API keys automatically using the official Model Context Protocol (MCP) server. See Connecting AI Agents to BlockVectra.
Upgrading limits: After topping up, the account-wide calls-per-second limit is removed; each key remains subject to Compute Unit (CU) rate and burst limits. For current rates and billing units, see the Pricing page.

Next steps

Browse the datasets directory to see every dataset BlockVectra indexes.
See the free plan and pricing to check what your account includes.
Log in to the console to create an API key.

Using BlockVectra on Robinhood Chain