Credits
Why use Credits?
Our subscriptions are based around "Credits" or "Compute Units", which provide a measure for the resources required to fulfill each request.
To demonstrate through an example, /v2/detailed-vaults/{network}/{vaultAddress}/apy
has a lower credit cost because it returns only the current APY on a single vault, while /v2/detailed-vaults
returns detailed TVL + APY datapoints across many vaults.
Credits by endpoint
General
/v2/vaults
1 credit
/v2/assets
1 credit
/v2/tags
1 credit
/v2/networks
1 credit
Detailed Vaults
/v2/detailed-vaults
1 base + 4 per vault requested
/v2/detailed-vaults/{network}/{vaultAddress}
3 credits
/v2/detailed-vaults/{network}/{vaultAddress}/apy
1 credit
/v2/detailed-vaults/{network}/{vaultAddress}/tvl
1 credit
Historical
/v2/historical/{network}/{vaultAddress}
4 base + 2 per historical point
/v2/historical/{network}/{vaultAddress}/apy
2 base + 1 per historical point
/v2/historical/{network}/{vaultAddress}/tvl
2 base + 1 per historical point
Portfolio
/v2/portfolio/best-vault/{userAddress}
2 credits
/v2/portfolio/positions/{userAddress}
5 credits
/v2/portfolio/positions/{userAddress}/{network}/{vaultAddress}
1 credit
/v2/portfolio/best-deposit-options/{userAddress}
1 base + 2 per vault requested
/v2/portfolio/returns/{userAddress}/{network}/{vaultAddress}
2 credits
/v2/portfolio/idle-assets/{userAddress}
5 credits
/v2/portfolio/events/{userAddress}/{network}/{vaultAddress}
3 credits
Transactions
/v2/transactions/context/{userAddress}/{network}/{vaultAddress}
3 credits
/v2/transactions/{action}/{userAddress}/{network}/{vaultAddress}
5 credits
Legacy (v1) API credits per endpoint
Looking for details on v1 endpoints? See here.
Last updated