DeFi Category Data by Chain | Toolmu

Get overview data for a type of decentralized finance (DeFi) app on one blockchain. Tell us which measure (such as fees), app type (such as decentralized exchanges), and blockchain (such as Ethereum) in everyday words.

Your AI

Use with your AI

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

CodexClaude CodeCursorWindsurfCline

View instructions

Map everyday measures to one supported metric: fees, liquidations, DEX volume, derivatives volume, options volume, aggregator volume, bridge-aggregator volume, open interest, or normalized volume. Resolve everyday app types to an exact DefiLlama category; for decentralized exchanges, use the documented category value dexs. Use the human blockchain name, such as Ethereum. The metric, category and chain are required; ask a short plain-language follow-up if any is missing, unsupported or ambiguous. Never ask the user for a metric code, category slug or API field name. Use the provider default data type unless the user clearly asks for a supported alternative. This endpoint returns an overview, not a chart or time series. Check the current price, balance and user authorization before calling get-category-chain-dimension-data-overview-defillama.

Task:
Tell me the [data you want, such as fees], [app type, such as decentralized exchanges], and [blockchain, such as Ethereum].

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

DeFi Category Data by Chain | Toolmu

Get overview data for a type of decentralized finance (DeFi) app on one blockchain. Tell us which measure (such as fees), app type (such as decentralized exchanges), and blockchain (such as Ethereum) in everyday words.

You receive

One run returns daily metric records for the metric, category, and chain you submit. Output fields are unpublished, so read the payload. Maximum $0.0006 per call. It does not return TVL, yields, prices, or charts.

Start with your task

Tell me the [data you want, such as fees], [app type, such as decentralized exchanges], and [blockchain, such as Ethereum].

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, category, chain`
chain`pathParams.chain`	`string`	Required	chain name Examples `Ethereum`
metric`pathParams.metric`	`string`	Required	The dimension metric type Options `fees, liquidations, dexs, derivatives, options, aggregators, bridge-aggregators, open-interest, normalized-volume` Examples `fees`
category`pathParams.category`	`string`	Required	category slug (slugified category name, e.g. 'dexs', 'prediction-market', 'options') Examples `dexs`
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",
        "category",
        "chain"
      ],
      "properties": {
        "chain": {
          "type": "string",
          "examples": [
            "Ethereum"
          ],
          "description": "chain name"
        },
        "metric": {
          "enum": [
            "fees",
            "liquidations",
            "dexs",
            "derivatives",
            "options",
            "aggregators",
            "bridge-aggregators",
            "open-interest",
            "normalized-volume"
          ],
          "type": "string",
          "examples": [
            "fees"
          ],
          "description": "The dimension metric type"
        },
        "category": {
          "type": "string",
          "examples": [
            "dexs"
          ],
          "description": "category slug (slugified category name, e.g. 'dexs', 'prediction-market', 'options')"
        }
      },
      "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.