# DefiLlama TVL

Any project that has implemented a functioning [DefiLlama adapter](https://github.com/DefiLlama/DefiLlama-Adapters/tree/main/projects) can configure KPI options to track its TVL measured in USD. In addition to [common ancillary data parameters](/kpi-options/kpi-option-configuration/common-ancillary-data-parameters.md) the deployer should configure DefiLlama TVL specific settings as documented below. Full specification of DefiLlama TVL data source is available in its [implementation document](https://github.com/UMAprotocol/UMIPs/blob/master/Implementations/defillama-tvl.md) to be referenced by verifiers.

### Endpoint

`Endpoint` string value should be set to project's DefiLlama TVL API endpoint in the format `"https://api.llama.fi/protocol/<PROJECT_SLUG>"` where `<PROJECT_SLUG>` should be replaced with project slug name used in DefiLlama TVL adapter.

### Metric Selector

In order to instruct verifiers on the location of TVL value within returned `Endpoint` response `Key` string parameter should be set to `tvl[i].totalLiquidityUSD where tvl[i].date is the latest daily timestamp before the evaluated timestamp`.

By default TVL across all chains would be tracked. If however the KPI metric was to track TVL on a particular chain additional optional `ChainName` string parameter should be set to the selected chain name. Names of supported chains can be observed as key names under the returned `chainTvls` object when querying the `Endpoint`.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.outcome.finance/kpi-options/kpi-option-configuration/defillama-tvl.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
