DeFi Volume & Fees — DefiLlama 📊

foXLabs crypto series: Token unlocks · Funding rates · Stablecoins · Hacks database

🎉 Turn DefiLlama into clean, structured DeFi volume & fees data — no login, no API key, one row per protocol, with trading volume, fees, revenue and chains. Built for DeFi analysts, traders and crypto research.

🔍 What is the DeFi Volume & Fees — and when should you use it?

Give this actor protocol names or chains and it returns matching protocols from DefiLlama volume and fees data (public DeFi analytics) — as clean, deduplicated rows you can filter, export or feed to an AI agent. Every run reads the source live.

Use it when you need: a protocol’s volume/fees/revenue; a chain’s DeFi activity; or a ranked table of protocols.

Use something else when: you need token price or on-chain balances — this is protocol volume/fees, not market or wallet data.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/defillama-volume-fees.

Your agent can pay for its own runs. This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over x402 (USDC on Base) or Skyfire — no Apify account or API token of its own. Billing is the same either way: per delivered record, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

I want to pull DeFi protocol company records using the Apify Actor `foxlabs/defillama-volume-fees`.
Input: `dataset`, `chain`, `category`, `minValue24h` and more — see the Input table below. `maxResults` caps how many results are returned.
Start with: {"dataset":"dex_volume","maxResults":500}
Ask me what to look up, run the Actor, then summarise the rows as a table.

The machine-readable API, MCP config and OpenAPI definition live at apify.com/foxlabs/defillama-volume-fees.md.

📋 Overview

Everything you need to turn DefiLlama volume and fees data (public DeFi analytics) into clean, structured data — in one actor, with no login, cookies or API key.

Why teams pick this actor:

• ✅ Whole feed, one call — name or ID in, matching protocols out.
• 🧹 No empty-promise columns — only fields this registry actually fills; degenerate columns are removed.
• 🔗 Stable identifiers — every row carries the source's own IDs, ready to join across runs and to other Fox Labs actors.
• 💰 Per-row pricing — a minimal price per delivered row, no subscription.
• 🤖 Agent-ready — MCP + x402 agentic payments.

✨ Features

• 🔍 Name or ID lookup — relevance-ranked name search or exact registry-ID lookup.
• 🏢 Full entity profile — status, legal form, formation date, address and the registry’s own contact fields.
• 🧹 Clean schema — deduplicated camelCase rows, ready for CSV/Excel/JSON.

🎬 Quick Start

curl -X POST "https://api.apify.com/v2/acts/foxlabs~defillama-volume-fees/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"dataset":"dex_volume","maxResults":500}'

🚀 Getting Started (3 steps)

1. Choose your targets — protocol names or chains.
2. Set the cap — maxResults limits how many results are returned.
3. Run and export — get a clean dataset as JSON, CSV or Excel.

📥 Input

{"dataset":"dex_volume","maxResults":500}

Field	Type	Description
dataset	string	Which DeFi leaderboard to export.
chain	string	Keep only protocols active on this chain (e.g. "Ethereum", "Solana", "Arbitrum", "Base", "BSC"). Leave empty for all chains.
category	string	Keep only this protocol category (e.g. "Dexs", "Lending", "Derivatives", "Liquid Staking"). Leave empty for all categories.
minValue24h	integer	Drop protocols whose 24h value (volume/fees/revenue/TVL depending on dataset) is below this USD threshold. 0 = no filter.
sortBy	string	Rank the leaderboard by this metric (descending).
maxResults	integer	Cap the number of rows returned (after filtering & sorting). The full lists are ~1,200 DEXs / ~2,400 fee protocols / ~7,800 TVL protocols.

📤 Output

One row per result, saved to the dataset. Every row carries scrapedAt. Lookups that cannot be completed are reported in the run log rather than silently dropped.

Field	Description
rank	Rank
dataset	Dataset
name	Name
category	Category
chainsText	Chains Text
dominantChain	Dominant Chain
chainCount	Chain Count
value24h	Value24h
value7d	Value7d
value30d	Value30d
change1dPct	Change1d Pct
change7dPct	Change7d Pct
change30dPct	Change30d Pct
logo	Logo
url	Url
generatedAtIso	Generated At Iso

💼 Use cases

1. Protocol screening — rank DeFi protocols by volume and fees. Input: protocol names or chains. Output: volume + fees + revenue. Use: a ranked table.

2. Chain analysis — compare DeFi activity across chains. Input: chain names. Output: per-chain metrics. Use: a chain scorecard.

3. Revenue tracking — watch a protocol’s fees over time. Input: protocol names, scheduled. Output: fees + revenue. Use: spot trends.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/defillama-volume-fees').call({"dataset":"dex_volume","maxResults":500});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/defillama-volume-fees').call(run_input={"dataset":"dex_volume","maxResults":500})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Automation (n8n / Zapier / Make): schedule or webhook → HTTP request to the actor API with your input → handle the JSON dataset → push to a sheet, CRM or dashboard.

📊 Pricing

Pay-per-event: per delivered record. Empty or failed lookups are never billed. View current pricing.

❓ FAQ

Do I need an account, login or API key? No. This reads DefiLlama volume and fees data (public DeFi analytics).

What do I search by? Protocol names or chains.

How current is the data? Every run queries the source live, so results are as fresh as the registry.

What metrics are included? Trading volume, fees, revenue and chain breakdown per protocol from DefiLlama.

Can I export to CSV / Excel / JSON? Yes — directly from the Apify dataset.

🐛 Troubleshooting

• Fewer rows than expected — raise maxResults, or refine the input.
• A name returns an unexpected entity — it matched a similar registered name; search the exact registry ID.
• No rows for a name — try the entity’s exact legal name or its registry ID.

⚖️ Is it legal to scrape this data?

This actor reads public on-chain / DeFi analytics from DefiLlama. Results can still contain personal data (e.g. a person’s name); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify’s blog post on the legality of web scraping.

🤝 Support & contact

• 🌐 Website: data.foxlabs.com.tr
• 📧 Email: info@foxlabs.com.tr
• 🐛 Issues: open a ticket in the Actor’s Issues tab
• 🧰 More clean B2B data actors: Fox Labs on Apify

Changelog

0.1.16 — 2026-09-20 — README examples corrected against the real input schema

• The README's code examples did not match this Actor. They used queries and maxResultsPerQuery — keys that do not exist in this Actor's input schema — with a placeholder value, and the input table listed those same phantom fields. Anyone who copied the AI-agent, cURL, JavaScript or Python example got a failing run. Every example now uses the real schema and matches the Console prefill: {"dataset":"dex_volume","maxResults":500}
• The input table is regenerated from input_schema.json, so it lists the fields the Actor actually accepts.
• Removed claims carried over from the same generator template where present: "formation / status monitoring", "a canonical registry record for KYB and due diligence", "every row carries query", and industry described as a NACE code.
• No code, output field or pricing change.

0.1 — 2026-09-07

• Enabled AI-agent payments (x402) + rebuilt the README to the full standard (What-is / when, AI-agents + x402 agentic payments + MCP, Overview, Features, Use cases, Integration, FAQ, Troubleshooting, Support & contact).

0.0

• Initial release: data from DefiLlama volume and fees data (public DeFi analytics) by name or registry ID.