> For the complete documentation index, see [llms.txt](https://node1.gitbook.io/node1-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://node1.gitbook.io/node1-docs/robinhood/robinhood-feed.md).

# Robinhood Feed

## Introduction

Sequencer Feed is a real-time data stream published by the Robinhood Chain sequencer. Nodes receive block data over WebSocket to follow the latest blocks and update their local chain state. Feed latency and connection stability affect how quickly nodes can stay in sync, making the feed useful for node operators and latency-sensitive applications.

Node1 provides two Feed formats in Ohio: Transaction Feed (one transaction per message) and Native Feed (original block messages, compatible with Nitro). Connect using the Account UUID associated with your active Feed subscription. See the [Connection Guide](/node1-docs/robinhood/robinhood-feed/robinhood-feed-connection.md) for URLs and the required Native Feed request header.

## Choose your connection

* **`/tx/<account_uuid>` — faster transaction delivery.** Each message contains one transaction, for bots and custom transaction processing.
* **`/feed/<account_uuid>` — node acceleration.** Messages use the original block-based Feed format, compatible with Robinhood Chain Nitro nodes. The WebSocket handshake requires `Arbitrum-Feed-Client-Version: 2`.

**Before using `/feed/` for node acceleration, you must first synchronize your node to the latest blocks through the official Robinhood Feed. Only then switch its Feed input to Node1.** After switching, monitor the node to ensure it continues to follow the latest blocks.

See the [Connection Guide](/node1-docs/robinhood/robinhood-feed/robinhood-feed-connection.md) for complete URLs and setup examples.

## Plans and pricing

| Plan    | Validity | Price             |
| ------- | -------- | ----------------- |
| Daily   | 24 hours | 200 USDC / USDG   |
| Weekly  | 7 days   | 900 USDC / USDG   |
| Monthly | 30 days  | 2,000 USDC / USDG |

Pay with **USDC on Solana** or **USDG on Robinhood Chain**. Select a payment network in the dashboard and follow the order's address, amount, and verification steps. Renewals extend an active subscription; purchases after expiry start from the new payment confirmation time. Feed and Landing subscriptions are independent.

## Subscribe & get your UUID

1. Sign in to the [Node1 Dashboard](https://node1.me/dashboard) and open Robinhood Feed.
2. Choose a plan and complete payment. Once payment is confirmed, check that your subscription status is Active.
3. Copy the Account UUID shown in the subscription panel and use it in the URL in the [Connection Guide](/node1-docs/robinhood/robinhood-feed/robinhood-feed-connection.md).

[Connect to the Feed →](/node1-docs/robinhood/robinhood-feed/robinhood-feed-connection.md)

## Performance

[View the Ohio feed benchmark →](/node1-docs/robinhood/robinhood-feed/robinhood-feed-benchmark.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://node1.gitbook.io/node1-docs/robinhood/robinhood-feed.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.