If you exceed your plan’s requests-per-minute limit, additional requests will still be processed if throughput autoscale is enabled. These extra requests also consume Compute Units. You can find the cost per extra request in the pricing table.
Not all rollups require the same computational power to process API requests. Some are lightweight, while others demand significantly more resources. To account for these variations, we apply a Rollup Multiplier to Compute Units (CUs), ensuring that pricing accurately reflects the underlying computational cost.
Method Responses × Rollups Multiplier = Compute Units (CUs)
This ensures that high-throughput rollups, which consume more resources, are fairly priced compared to smaller chains. By aligning costs with computational intensity, Rollup Multipliers prevent inefficiencies, optimize pricing, and help developers scale seamlessly.
