Overview

All of our API endpoints are metered in Compute Units (CU).

Each one of our subscription plans comes with a certain amount of CUs included. If you exceed your CUs for a given month, overages will apply. You have the option to disable this for your account, which means that once you exceed your allocated CUs, the API key will be disabled until the next billing cycle.

Fixed vs Variable CU Cost

Note that some endpoints have a fixed cost per API call, and some have a variable cost that depends on how many items are returned (this most typically applies to the txs endpoints, where the total amount of CUs billed will depend on how many transactions are returned).

Example

For example, if you call txs on EVM with a pageSize of 50 and you retrieve 50 transactions on that call, your CU cost will be:

25 * 50 = 1250 CUs

If you make that same call passing a pageSize of 50 but there aren't 50 items to return, you'll only be billed for the transactions actually returned. So if you only get 10 transactions back, your CU cost will be 250.

Compute Unit Cost Table

EVM

Translate

*The CU costs for balancesOf on EVM are determined by chain, see the table at the end of this document for details.

Pricing

SVM

Translate

Pricing

Cosmos

Translate

Pricing

TVM

Translate

*As this endpoint works based on ad-hoc indexing of transactions, the actual cost is calculated at 1 CU per every 200 transactions indexed

Polkadot

Translate

UTXO

Translate

Move

Pricing

Appendix

EVM balancesOf costs by chain