Compute Units
Why use Compute Units?
Our subscriptions are based around Compute Units, which provide a measure for the resources required to fulfill each request.
To demonstrate through an example, an endpoint such as Vault APY is lighter weight than an endpoint like [PRO] Vault Range Historical Data. The Vault APY endpoint returns a single APY at a point in time, while the Vault Range Historical Data endpoint can return a wealth of data for many points of time, including detailed metrics for base vs. rewards APY and liquid/locked TVL over requested intervals spanning weeks or months.
Weights by endpoint
# credits per call | |
---|---|
General endpoints | |
/v1/vaults | 2 |
/v1/tags | 2 |
/v1/tokens | 2 |
/v1/networks | 2 |
/v1/detailed/vaults | 4 |
Vault endpoints | |
/v1/vaults/{network}/{vaultAddress}/ | 4 |
/v1/vaults/{network}/{vaultAddress}/apy | 2 |
/v1/vaults/{network}/{vaultAddress}/historical-tvl/{timestamp} | 2 |
/v1/vaults/{network}/{vaultAddress}/historical-apy/{timestamp} | 2 |
Pro endpoints | |
/v1/vaults/{network}/{vaultAddress}/historical-apy | 8 |
/v1/vaults/{network}/{vaultAddress}/historical-data | 16 |
Other | |
/v1/health | 1 |
Last updated