Robinhood Chain public RPC vs a keyed endpoint
Last updated:
Side by side
| Property | Public Robinhood endpoint | Triport (keyed) |
|---|---|---|
| URL | https://rpc.mainnet.chain.robinhood.com (chain ID 4663) | https://triport.io/rpc/robinhood with a key; wallets use https://triport.io/r/<API_KEY>/robinhood |
| Access | Open URL, no key | API key with scopes (robinhood:rpc, robinhood:feed); no key gets HTTP 401 |
| Keyless option | The URL itself | Triport keyless https://triport.io/public/robinhood: 15 req/s reads (debug_* traces included) and 3 req/s sends, one budget shared by every caller, no WebSocket and no feed |
| Request rate | Rate-limited, figure not published (checked 2026-10-13) | Per-category RPS limits by plan: reads 15/20/100/250 sustained RPS (burst 30/40/200/500), submission 3/5/30/80 (burst 6/10/60/160; default, unmeasured) |
| Body and batches | Not published | JSON-RPC body and batch up to 4 MiB; each element checked, N elements cost N requests |
| JSON-RPC WebSocket | Not published for the public endpoint | newHeads and logs from Basic, with documented close codes |
| Sequencer feed | wss://feed.mainnet.chain.robinhood.com (checked 2026-10-13) | From Pro: resume by ?from_sequence= with earliest/latest bounds and bufferComplete; optional early_heads=1 |
| Feed fallback | Delayed backup feed wss://delayed-feed.mainnet.chain.robinhood.com: behind the primary, on separate capacity, the network's recommended fallback (checked 2026-10-13) | Reconnect to the same feed with ?from_sequence=: the replay window keeps up to five minutes (8,192 frames, 64 MiB), and bufferComplete says when it does not cover the gap |
| Method surface | Standard EVM JSON-RPC | 27 catalogued methods with published statuses: debug_* best-effort without SLA, submission routed to the sequencer intake |
| Production guidance | Network says "not recommended for production use" (checked 2026-10-13) | Documented contract, limits and error codes per surface |
| Testnet | https://rpc.testnet.chain.robinhood.com, chain ID 46630 (checked 2026-10-13) | Mainnet only (chain ID 4663) |
| Price | Free | Flat monthly plan, no compute units, no per-call credits |
When the public endpoint is the right choice
For a one-off script, a local experiment or a first look at the chain, the open endpoint is the shortest path: no account, no key, nothing to configure. Reading a couple of blocks or checking a balance needs nothing more.
Triport also has a keyless Robinhood Chain URL for exactly this kind of first look: https://triport.io/public/robinhood, with 15 req/s of reads — debug_* traces included — and 3 req/s of sends, shared by every caller, with no WebSocket and no feed. Every other Triport URL needs an API key and answers HTTP 401 without one; the 7-day Free trial key is the way to try those. See public RPC and the free trial key.
When to move to a keyed endpoint
- Your traffic is steady rather than occasional and you need a request rate you can plan against.
- You send wide
eth_getLogsqueries or JSON-RPC batches and need the 4 MiB body ceiling with per-element accounting. - You want
newHeadsorlogssubscriptions with documented close codes instead of polling. - You consume the sequencer feed and need to resume after a disconnect by cursor, with an explicit signal when the window cannot cover the gap.
- You need the method surface and its limits written down — including where we say a capability is best-effort.
What Triport does not claim
Our debug_* trace methods are best-effort and carry no availability SLA; archive depth is measured, not a full-history guarantee; a submitted transaction's hash means it was routed, and the receipt decides inclusion. Those limits are on the method pages, not hidden in a footnote. Robinhood Chain is also served by several other infrastructure providers listed in the network's documentation; this page compares Triport with the network's public endpoint only, and makes no claim about any other provider.
2× burst buffer, included. Finite request-rate limits show sustained RPS and short burst capacity. A full buffer at 20 RPS can absorb up to 40 requests at once and refills at 20 requests per second. There is no quota on the number of bursts and no extra charge for them. Size ongoing traffic to sustained RPS. Categories with no per-category cap have no numeric burst ceiling. How burst capacity works.
FAQ
- What is the public Robinhood Chain RPC URL?
- https://rpc.mainnet.chain.robinhood.com for JSON-RPC on mainnet, chain ID 4663. The network also publishes a sequencer feed at wss://feed.mainnet.chain.robinhood.com and a delayed backup feed at wss://delayed-feed.mainnet.chain.robinhood.com, and documents all of its public endpoints as rate-limited and "not recommended for production use" (checked 2026-10-13).
- What is the delayed feed for?
- The network describes wss://delayed-feed.mainnet.chain.robinhood.com as a backup that runs behind the primary feed on separate capacity and recommends it as the fallback (checked 2026-10-13). It is mainnet-only; the testnet lists no delayed feed.
- Is the public endpoint enough for production?
- By the network's own guidance, no: it states the public endpoints are "rate-limited and not recommended for production use. For production, use a provider" (checked 2026-10-13). The endpoint publishes no per-key quota, no support path and no availability commitment.
- What does a keyed Triport endpoint add?
- A key with scopes and a documented per-plan request rate, JSON-RPC bodies and batches up to 4 MiB with every batch element checked, newHeads and logs subscriptions from Basic, and a sequencer feed from Pro that resumes by cursor with an explicit bufferComplete flag.
- Does Triport proxy the Robinhood testnet?
- No. Testnet chain 46630 has its own public endpoint, https://rpc.testnet.chain.robinhood.com, but Triport serves mainnet (chain ID 4663) only — use the network's testnet endpoint for test work.
- What happens if I call Triport without an API key?
- On the keyed URLs the request is refused with HTTP 401 and a JSON body that names the two ways to pass a key: ?api-key=<key> in the URL or an Authorization: Bearer header. For a test without a key there is https://triport.io/public/robinhood: 15 req/s reads (debug_* traces included) and 3 req/s sends, one budget shared by every caller, no WebSocket and no feed; a 7-day Free trial key gives you a budget of your own and WebSocket.
- How is Triport priced against a free public endpoint?
- The public endpoint costs nothing and guarantees nothing. Triport is a flat monthly plan — Basic $20, Pro $249, Business $499, Enterprise from $999 — with no compute units and no per-call credits: you buy throughput, not request counts. Our Free is a 7-day trial, not a permanent free plan.