Get protocol timeseries chart data breakdown by version

Get protocol timeseries chart data breakdown by version. Supply pathParams.metric, pathParams.protocol. A field-level output specification is not published in this Tool's current contract. The native run result is the authority for returned data. This draft does not promise unobserved fields, complete coverage or a guaranteed match. Current ceiling: 0.000720 credits. Use one Toolmu account and shared balance across available Tools. Pay per use; no required subscription. The credit ceiling is separate from monetary values returned in the data.

Your AI

Use with your AI

For tasks with several steps, continue in the AI you already use.

CodexClaude CodeCursorWindsurfCline

View instructions

Get protocol timeseries chart data breakdown by version. Complete this task using the exact Toolmu Tool below. Reuse a working Toolmu connection; if needed, follow https://toolmu.com/SKILL.md. Read its current contract, ask for missing required input, verify availability, current price, balance and budget, then execute within the user authorization and explain the returned result. Do not create a replacement for UNKNOWN or an unconfirmed run.
Tool: get-protocol-timeseries-chart-data-breakdown-by-version-defillama
Supply pathParams.metric, pathParams.protocol.

Task:
Name one crypto project, such as [Aave], and say what you want to compare across its versions, like fees or revenue. I’ll show how the figures changed over time. If more than one project matches, I’ll ask you to choose.

Paste into your connected AI's conversation.

Connection guide

Up to 0.00072 credits / call

The final charge is based on confirmed usage. Unused reserved credits return to your available balance.

DefiLlama

Get protocol timeseries chart data breakdown by version

You receive

Get protocol timeseries chart data breakdown by version. A field-level output specification is not published in this Tool's current contract. The native run result is the authority for returned data. This draft does not promise unobserved fields, complete coverage or a guaranteed match.

Start with your task

Name one crypto project, such as [Aave], and say what you want to compare across its versions, like fees or revenue. I’ll show how the figures changed over time. If more than one project matches, I’ll ask you to choose.

Inputs & outputs

Inspect the current inputs, availability, and maximum charge before starting.

Input schema

Input schema
Field / Path	Type	Requirement	Meaning
pathParams`pathParams`	`object`	Required	Required fields `metric, protocol`
metric`pathParams.metric`	`string`	Required	The dimension metric type Options `fees, liquidations, dexs, derivatives, options, aggregators, bridge-aggregators, open-interest, normalized-volume` Examples `fees`
protocol`pathParams.protocol`	`string`	Required	protocol slug (slugified protocol name) Examples `aave`
queryParams`queryParams`	`object`	Optional
dataType`queryParams.dataType`	`string`	Optional	Metric-specific data type to return. Supported values per metric: - fees: dailyFees (default), dailyRevenue, dailySupplySideRevenue, dailyHoldersRevenue, dailyProtocolRevenue - liquidations: dailyLiquidationsVolume (default), dailyCollateralLiquidated - dexs: dailyVolume (default), dailyNotionalVolume - derivatives: dailyVolume (default), dailyNotionalVolume - options: dailyNotionalVolume (default), dailyPremiumVolume - aggregators: dailyVolume (default) - bridge-aggregators: dailyBridgeVolume (default) - open-interest: openInterestAtEnd (default), shortOpenInterestAtEnd, longOpenInterestAtEnd - normalized-volume: dailyNormalizedVolume (default), dailyActiveLiquidity Examples `dailyFees`

View raw JSON

{
  "type": "object",
  "required": [
    "pathParams"
  ],
  "properties": {
    "pathParams": {
      "type": "object",
      "required": [
        "metric",
        "protocol"
      ],
      "properties": {
        "metric": {
          "enum": [
            "fees",
            "liquidations",
            "dexs",
            "derivatives",
            "options",
            "aggregators",
            "bridge-aggregators",
            "open-interest",
            "normalized-volume"
          ],
          "type": "string",
          "examples": [
            "fees"
          ],
          "description": "The dimension metric type"
        },
        "protocol": {
          "type": "string",
          "examples": [
            "aave"
          ],
          "description": "protocol slug (slugified protocol name)"
        }
      },
      "additionalProperties": true
    },
    "queryParams": {
      "type": "object",
      "properties": {
        "dataType": {
          "type": "string",
          "examples": [
            "dailyFees"
          ],
          "description": "Metric-specific data type to return. Supported values per metric:\n- **fees**: dailyFees (default), dailyRevenue, dailySupplySideRevenue, dailyHoldersRevenue, dailyProtocolRevenue\n- **liquidations**: dailyLiquidationsVolume (default), dailyCollateralLiquidated\n- **dexs**: dailyVolume (default), dailyNotionalVolume\n- **derivatives**: dailyVolume (default), dailyNotionalVolume\n- **options**: dailyNotionalVolume (default), dailyPremiumVolume\n- **aggregators**: dailyVolume (default)\n- **bridge-aggregators**: dailyBridgeVolume (default)\n- **open-interest**: openInterestAtEnd (default), shortOpenInterestAtEnd, longOpenInterestAtEnd\n- **normalized-volume**: dailyNormalizedVolume (default), dailyActiveLiquidity"
        }
      },
      "additionalProperties": true
    }
  },
  "additionalProperties": false
}

Result schema

Output fields have not been documented yet.

Additional notes

What this Tool does

Get protocol timeseries chart data breakdown by version. Supply pathParams.metric, pathParams.protocol.

Inputs and conditions

pathParams — object; Required.

pathParams.metric — string; Required. The dimension metric type {"enum":["fees","liquidations","dexs","derivatives","options","aggregators","bridge-aggregators","open-interest","normalized-volume"]}

pathParams.protocol — string; Required. protocol slug (slugified protocol name)

queryParams — object; Optional.

queryParams.dataType — string; Optional. Metric-specific data type to return. Supported values per metric: - **fees**: dailyFees (default), dailyRevenue, dailySupplySideRevenue, dailyHoldersRevenue, dailyProtocolRevenue - **liquidations**: dailyLiquidationsVolume (default), dailyCollateralLiquidated - **dexs**: dailyVolume (default), dailyNotionalVolume - **derivatives**: dailyVolume (default), dailyNotionalVolume - **options**: dailyNotionalVolume (default), dailyPremiumVolume - **aggregators**: dailyVolume (default) - **bridge-aggregators**: dailyBridgeVolume (default) - **open-interest**: openInterestAtEnd (default), shortOpenInterestAtEnd, longOpenInterestAtEnd - **normalized-volume**: dailyNormalizedVolume (default), dailyActiveLiquidity

Returned information

A field-level output specification is not published in this Tool's current contract. The native run result is the authority for returned data. This draft does not promise unobserved fields, complete coverage or a guaranteed match.

Price and account

Current published execution ceiling: 0.000720 credits. Use one Toolmu account and shared balance across available Tools. Pay per use; no required subscription. The credit ceiling is separate from monetary values returned in the data.

Limits and freshness

Results depend on the supplied input and the provider's coverage at execution time. Missing records, null fields or a limited result set do not prove that an entity does not exist. A saved Example is historical; viewing it does not execute this Tool.

Source and verification

Contract and price verified through Toolmu MCP on 2026-10-02T02:35:33.570Z (UTC). Toolmu Tool: get-protocol-timeseries-chart-data-breakdown-by-version-defillama.

https://api-docs.defillama.com/

Questions about this tool.

Inputs, results and details to know before running it.

Get connected

Get protocol timeseries chart data breakdown by version. Supply pathParams.metric, pathParams.protocol.

Get protocol timeseries chart data breakdown by version

Get protocol timeseries chart data breakdown by version

You receive

Start with your task

Inputs & outputs

Input schema

Result schema

What this Tool does

Inputs and conditions

Returned information

Price and account

Limits and freshness

Source and verification

Compare daily fees for [Aave] across versions

Compare [Aave V2] and [Aave V3] fees

View [Aave] revenue by version

Questions about this tool.

You receive

Start with your task

Inputs & outputs

Input schema

Result schema

What this Tool does

Inputs and conditions

Returned information

Price and account

Limits and freshness

Source and verification

Compare daily fees for [Aave] across versions

Compare [Aave V2] and [Aave V3] fees

View [Aave] revenue by version

Questions about this tool.

What input does this Tool need?

What does the result prove?

How is this Tool charged?

What if the result is empty or a field is missing?

How do I use this Tool with my Agent?