vaults.fyi
  • General
    • 🏦Overview
    • 🔎Methodology
      • vaults.fyi USD benchmark rate
      • vaults.fyi ETH benchmark rate
    • ❓FAQ
      • Vault requirements for inclusion on vaults.fyi
  • API
    • vaults.fyi API Overview
      • Insights API
      • Earn API
        • Product demo
        • Flow diagrams
      • Plans
        • Credits
    • Endpoints
      • Market data
        • Get historical data
          • Get historical data on single vault
          • Get historical TVL on single vault
          • Get historical APY on single vault
        • Get data for multiple vaults
        • Get data on single vault
          • Get APY on single vault
        • Get benchmark rates
        • Get supported vaults, networks & tokens
          • /vaults
          • /networks
          • /tokens
          • /tags
      • Contextual insights
        • Top vault options for address
        • Get single top option for address
        • [Etherscan cards] Get top USD, top ETH vault for address
      • Transactional (Earn API)
        • Prepare transaction calldata
          • Deposit
          • Redeem
            • Request redeem
            • Claim redeem
          • Claim rewards
        • Get transaction prep details
        • Get supported assets
        • Get supported vaults
      • Position tracking (Portfolio API)
        • Get user balances
        • Get user positions
        • Get list of past vault txns by user address
        • Get estimated returns for user's vault position
  • Case Study: Etherscan Cards
  • Links
    • vaults.fyi
    • X
    • Farcaster
    • Wallfacer Labs
Powered by GitBook
On this page
  • Why use Credits?
  • Weights by endpoint
  1. API
  2. vaults.fyi API Overview
  3. Plans

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, /v1/vaults/{network}/{vaultAddress}/apy is lighter weight than an endpoint like /v1/vaults/{network}/{vaultAddress}/historical-apy.

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.

Weights by endpoint

Endpoint
Credit Cost

GET /v1/vaults

1 credit

GET /v1/tags

1 credit

GET /v1/tokens

1 credit

GET /v1/networks

1 credit

GET /v1/detailed/vaults

Variable — 7 credits per vault requested

GET /v1/benchmarks

3 credits

GET /v1/vaults/{network}/{vaultAddress}/

3 credits

GET /v1/vaults/{network}/{vaultAddress}/apy

1 credit

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-events/{holder}

3 credits

GET /v1/vaults/{network}/{vaultAddress}/holder-total-returns/{holder}

2 credits

GET /v1/vaults/{network}/{vaultAddress}/historical-apy

2 credits base + 0.1 per data point

GET /v1/vaults/{network}/{vaultAddress}/historical-data (variation)

4 credits base + 2 per data point

GET /v1/transactions/vaults/actions/details

3 credits

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/transactions/assets

3 credits

GET /v1/transactions/vaults

3 credits

POST /v1/portfolio/best-deposit-options/{userAddress}

Variable — 2 credits per vault requested

POST /v1/portfolio/best-vault/{userAddress}

2 credits

GET/v1/portfolio/wallet-balances

5 credits

GET /v1/portfolio/positions/{userAddress}

5 credits

PreviousPlansNextEndpoints

Last updated 1 day ago