Robinhood ChainConnect your application through RPC and WebSocket, or query decoded history with SQL.
Use RPC and WebSocket for backend requests and subscriptions, or query decoded historical tables with SQL.
Read chain state, blocks, transactions and logs through standard Ethereum JSON-RPC. Subscribe to new block headers and filtered logs over WebSocket.
Connect from your backend. Authentication requires an x-token header; direct browser connections are restricted. Check method and history limits in the RPC docs.
Query decoded swaps, pools, token metadata and launchpad activity. Work with parsed records in SQL without building a log decoder for those datasets.
Check the documented tables and their available history for your analysis. SQL access uses separate credentials provisioned by the team.
Choose node requests and subscriptions or historical SQL records for the task below.
RPC / WebSocket · Make on-demand requests from your backend. Subscribe to block headers and logs for the events your application follows.
Historical Indexer · Analyze swaps, discover pools or study token launches with SQL against the available historical tables.
View pricing for each service, then use the links to its setup guides below.
Start in the portal for RPC access. Follow the RPC connection guide for HTTPS and WebSocket authentication, then integrate from your backend.
Start in the portal and discuss your tables and queries with the team, who will provide your host, port and credentials. Follow the Indexer connection instructions for your SQL client.
Match the interface, integration requirements and historical data to your workload.
Use RPC / WebSocket for node requests and subscriptions. Use the Historical Indexer for parsed datasets you can query with SQL. Check the documented data and methods against your task.
Connect through your backend. WebSocket authentication requires an x-token handshake header, and HTTPS does not support browser CORS preflight. See the RPC connection guide.
The Indexer exposes documented datasets for swaps, pools, tokens and launchpad activity. Review the table reference and confirm the history you need with the team before planning your analysis.
RPC uses token authentication. The Indexer is provisioned separately with its own SQL credentials. Follow the access instructions for each product; ask the team if your workload needs both.