Skip to main content
Every vaults.fyi API request consumes Credits. Credits — also called Compute Units (CUs) — measure the compute resources consumed by each request. Subscription plans include a monthly Credit budget, while pay as you go charges a flat $0.002 per credit. This model lets you pay proportionally for what you actually use, rather than treating a simple lookup the same as a rich multi-vault data pull.

​
How Credits Work

Each API call consumes Credits in two parts:
  • Base CU per call — a fixed cost charged for every request to that endpoint, regardless of how many results are returned.
  • CU per datapoint returned — an additional cost multiplied by the number of records in the response.
Example: /v2/detailed-vaults has a base cost of 1 CU plus 3 CU per vault returned. If your query returns 50 vaults, the total cost is 1 + (50 × 3) = 151 CUs. By contrast, /v2/detailed-vaults/{network}/{vaultAddress}/apy costs only 1 CU total because it returns a single APY value for a single vault.
To minimize credit consumption, use targeted single-vault endpoints when you only need data for a specific address, and use the list endpoints when you need to compare across many vaults.

​
v2 Endpoint Credit Costs

​
General

​
Detailed Vaults

​
Benchmarks

​
Historical

​
Portfolio

All plans can access portfolio endpoints.

​
Transactions

All plans can access transaction endpoints.

​
Beta Endpoint Credit Costs

Beta endpoints use the same base-cost and per-datapoint model as v2 endpoints.

​
Legacy v1 API Credits

The v1 API uses a simpler flat-credit model — each endpoint has a single fixed cost with no per-datapoint multiplier, except for a few endpoints that scale with the number of results requested.
The v1 (legacy) API endpoints remain fully supported and maintained. You can access the full v1 documentation in the Legacy v1 Endpoints reference.