Credits (v1 endpoints)
Last updated
Last updated
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, is lighter weight than an endpoint like .
The /apy endpoint returns a single APY at a point in time, while the /historical-apy 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.
GET /v1/vaults
1 credit
GET /v1/tags
1 credit
GET /v1/tokens
1 credit
GET /v1/networks
1 credit
GET /v1/vaults/{network}/{vaultAddress}/apy
1 credit
GET /v1/detailed/vaults
1 credit base + 4 credits per vault requested
GET /v1/vaults/{network}/{vaultAddress}/historical-tvl/{timestamp}
2 credits
GET /v1/vaults/{network}/{vaultAddress}/historical-apy/{timestamp}
2 credits
GET /v1/vaults/{network}/{vaultAddress}/holder-total-returns/{holder}
2 credits
POST /v1/portfolio/best-vault/{userAddress}
2 credits
GET /v1/vaults/{network}/{vaultAddress}/historical-apy
2 credits base + 1 per data point
POST /v1/portfolio/best-deposit-options/{userAddress}
2 credits per vault requested
GET /v1/benchmarks
3 credits
GET /v1/vaults/{network}/{vaultAddress}/
3 credits
GET /v1/transactions/vaults/actions/details
3 credits
GET /v1/vaults/{network}/{vaultAddress}/holder-events/{holder}
3 credits
GET /v1/transactions/assets
3 credits
GET /v1/transactions/vaults
3 credits
GET /v1/vaults/{network}/{vaultAddress}/historical-data
4 credits base + 2 per historical point
POST /v1/transactions/vaults/deposit
5 credits
POST /v1/transactions/vaults/redeem
5 credits
POST /v1/transactions/vaults/request-redeem
5 credits
POST /v1/transactions/vaults/claim-redeem
5 credits
POST /v1/transactions/vaults/claim-rewards
5 credits
GET/v1/portfolio/wallet-balances
5 credits
GET /v1/portfolio/positions/{userAddress}
5 credits