rpc-optimize
Installation
SKILL.md
RPC Optimization
The one thing most people get wrong
JSON-RPC batching does not save you money. It merges HTTP round-trips. Every provider that documents the rule bills each method inside the batch:
- Alchemy:
batch* | CU of method # times called - Ankr: "every sub-call in a batch is billed and rate-limited individually"
- QuickNode: "batching also counts as CPS because each request is counted individually"
- Infura: bills the batch N+1 — "if the array contains 30 requests… this would be 31 total requests." Batching on Infura is strictly worse than serial.
- Helius: documents no batch rule at all. Do not claim one either way.
What saves money is aggregation — collapsing N logical reads into 1 billable
method call. Measured, not estimated (benchmarks/, run 2026-08-04):