Skip to main content

Overview

grpc.raze.bot exposes a Yellowstone Geyser gRPC feed (Dragon’s Mouth) — the same geyser.Geyser/Subscribe interface used by the major Solana data providers. It is the lowest-latency way to consume raw account, slot, transaction, block and entry updates from Raze, and is fully compatible with the standard yellowstone-grpc client libraries.
For higher-level, pre-parsed events (trades, deploys, migrations, alerts) use the Streaming WebSocket API at wss://ws.raze.bot/ws/sol. Use gRPC when you want the raw geyser stream and minimum latency.

Authentication

Pass your API key as the x-token gRPC metadata header on the channel. This is the same key you use as X-Api-Key / ?apikey= on the REST and RPC endpoints — only the header name differs (Yellowstone clients call it x-token).
Requests without a valid token are rejected with UNAUTHENTICATED.

Subscribe

A single Subscribe bidirectional stream carries every update type. Filter by account, transaction, slot, block, blockMeta or entry in the SubscribeRequest.

Update types

The SubscribeRequest accepts the standard Yellowstone filter maps; set the ones you need and leave the rest empty: commitment may be PROCESSED, CONFIRMED or FINALIZED.
Transactions cost roughly 10× the bandwidth of account updates — scope your filters (accountInclude, accountRequired) as tightly as possible to keep latency low.