Our API Suite tiers are based on the number of compute units used. Every API method across each API consumes Compute Units.
Compute Units are a measure of the computing cost of each method. For example, eth_protocolVersion carries a low compute cost. Conversely, eth_estimateGas is more intensive computationally, giving it a higher cost.
Each method is allocated a number of Compute Units. Users will only pay for what they use, meaning no overpaying for low Compute Unit methods.
Following is a list of all the transaction categories and their associated Compute Unit costs:
| Transaction Category | Associated Compute Unit Costs |
|---|---|
| XS | 1 |
| S | 5 |
| M | 10 |
| L | 50 |
| XL | 100 |
| Egress | Custom |
| Batch Queries | Custom |
By weighing each method, Blockdaemon can best match developers with the right level of service they need. Our API Dashboard allows you to keep track of your Compute Units usage over time easily.
For details of Compute Units of specific endpoints, visit the relevant API sections.