Robinhood limits
The following rows come from the Robinhood entries in tier-matrix.yaml. Every numeric value is an unmeasured operational default, not measured upstream or Triport capacity. Re-measurement through the Triport path is tracked as N5-D-rh-C.
| Category | Free | Basic | Pro | Business | Enterprise | Status |
|---|---|---|---|---|---|---|
robinhood_read_rpc | 15 | 20 | 100 | 250 | unlimited | unmeasured |
robinhood_read_rpc_heavy | 15 | 20 | 100 | 250 | unlimited | unmeasured |
robinhood_send_tx | 3 | 5 | 30 | 80 | unlimited | unmeasured |
JSON-RPC request bodies and batches
POST /rpc/robinhood accepts JSON-RPC objects and batch arrays with a total
JSON body size up to 4 MiB (4,194,304 bytes), including whitespace. The
same limit applies to all API keys and is independent of requests per second.
Standard JSON-RPC arrays, including a one-element array, support large
eth_getLogs wallet-topic filters within this limit.
Every batch element is inspected for method and tier access. Where an RPS
budget applies, a batch of N requests costs N requests. Raising the RPS budget
does not raise the body-size limit. Oversized batches return HTTP 413 with
error: batch_too_large; split them into smaller arrays. Method-specific
parameter, response-size, and execution-time limits still apply.
Streaming access
| Surface | Free | Basic | Pro | Business | Enterprise | Status |
|---|---|---|---|---|---|---|
newHeads, logs WebSocket | unavailable | available | available | available | available | tier policy |
| Sequencer feed | unavailable | unavailable | 2 streams | 4 streams | 4 streams | unmeasured product limit |
The feed requires the robinhood:feed scope. These concurrency limits do not claim upstream capacity. See the shared Rate Limits and Tiers reference for quota headers, burst behavior, and product errors.
eth_getLogs also has channel-specific range and result ceilings. Triport may split or reconstruct deep ranges from receipts; reconstruction is slower and can still fail when no eligible historical channel exists.