Prediction Market Volume by Protocol | DefiLlama

Set the category to prediction-market and choose a supported volume metric to retrieve its time series split by protocol. You can also use the same endpoint for other supported DefiLlama metric and category pairs.

Your AI

Use with your AI

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

CodexClaude CodeCursorWindsurfCline

View instructions

Use `get-category-timeseries-chart-data-breakdown-by-protocol-defillama` for historical data matching the user’s chosen measure and app category, with separate results for each app. Map plain terms such as trading volume or fees and app descriptions such as prediction market platforms or crypto exchange apps to supported choices. If either choice is missing or unclear, ask one short question. Do not ask for a blockchain, date range, code, or ID. Explain only what the returned series shows.

Task:
Show how [trading volume] changes over time for [prediction market apps like Polymarket], with a separate result for each app.

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

Prediction Market Volume by Protocol | DefiLlama

Set the category to prediction-market and choose a supported volume metric to retrieve its time series split by protocol. You can also use the same endpoint for other supported DefiLlama metric and category pairs.

You receive

Returns category time-series data broken down by protocol, including prediction-market volume when you select that category and a supported volume metric. Not market odds, trades, token prices, TVL, or a live dashboard. No date-range filter. Output fields are unpublished; maximum $0.0006 per call.

Start with your task

Show how [trading volume] changes over time for [prediction market apps like Polymarket], with a separate result for each app.

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`
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"
      ],
      "properties": {
        "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.