max_batch_requests). Each item is validated and routed independently with bounded concurrency and its own execution deadline. Results appear in request order. Valid notifications produce no response item; an all-notification batch returns HTTP 204 with no body.
Use unique IDs for unambiguous correlation. A batch does not pin all items to one upstream or create an atomic state snapshot. Specify block selectors where your application needs a particular state reference.
Execution safety applies per item. eth_sendRawTransaction receives one upstream dispatch; placing it in a batch does not make replay safe. Subscription methods require WebSocket. See Supported methods.