For the complete documentation index, see llms.txt. This page is also available as Markdown.

Robinhood Chain Direct Sequencer Feed Integration Guide

Explore the services, price, endpoint and integration guide of the BlockRazor Robinhood Chain Direct Sequencer Feed.

What Is the Direct Sequencer Feed?

Compared with the Node-required Sequencer Feed, the Direct Sequencer Feed does not require node deployment. Standard clients can receive the latest blocks directly, enabling lower-latency tracking of on-chain signals. It is well suited for use cases such as sniping and copy trading that do not depend on full node state synchronization.

Please note that the Direct Sequencer Feed may skip blocks during periods of network congestion.

What is the difference between the Node-required Sequencer Feed and the Direct Sequencer Feed?
Comparison
Node-required Sequencer Feed
Direct Sequencer Feed

Access Method

Must be received through a node

Clients can connect directly without running a nod

Block Delivery

Delivers blocks sequentially by block height without skipping any blocks

Prioritizes the latest block; intermediate blocks may be skipped during network congestion

Node State Dependency

Relies on the node’s low-latency synchronized state

Does not require a local node to maintain complete and continuous state synchronization

Deployment Cost

Requires node deployment, maintenance, and monitoring

Easy to integrate, with lower operational costs

Suitable Use Cases

Backrunning and order flow projects

Sniping and copy trading

High-Performance JSON Parsing

Go clients connecting to the Robinhood Chain Direct Sequencer Feed can use ByteDance Sonic to parse JSON messages received over WebSocket. Sonic uses JIT compilation and SIMD acceleration to reduce parsing latency and CPU overhead in latency-sensitive trading systems.

In our benchmarks, Sonic achieved a P50 JSON parsing latency of approximately 2–3 microseconds. Actual performance may vary depending on message size, data structure, CPU architecture, and runtime environment. We recommend benchmarking with real feed data and warming up commonly used Go types before processing latency-sensitive traffic.

Our current reference implementation is written in Go. For trading strategies written in Rust, C++, or other languages, developers can use the above latency as a reference when selecting and benchmarking an equivalent high-performance JSON parsing library.

Price

The price is $80 per unit per day and $800 per unit per month. Subscribe

Endpoint

Region
Endpoint

Ohio

ws://us.robinhood-feeder.blockrazor.io/ws/direct/{authToken}

Region
Endpoint

Ohio

wss://us.robinhood-feeder.blockrazor.io/ws/direct/{authToken}

Tokyo

wss://jp.robinhood-feeder.blockrazor.io/ws/direct/{authToken}

Usage Instructions

1

Subscribe BlockRazor Sequencer Feed

2

Retrieve the auth from the portal and append it as the URI to the WS URL.

ws://us.robinhood-feeder.blockrazor.io/ws/direct/{authToken}

3

Choose a WebSocket Client and Establish a WSS Connection

Use any standard WebSocket client, such as a WebSocket library for Node.js, Go, Python, or Rust. There is no need to deploy a Robinhood Chain node or configure --node.feed.input.url.

4

Receive and parse the data. The parsed data structure is as follows:

Last updated

Was this helpful?