DeFi Volume & Fees — DefiLlama 📊

🎉 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 queries the source live, so the data is as fresh as the registry itself.

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: `queries` is a list of protocol names or chains. `maxResultsPerQuery` caps rows per query.
Start with: {"queries":["undefined"],"maxResultsPerQuery":50}
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.
• 💰 Pay only for results — per-row pricing, empty/failed lookups never billed.
• 🤖 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 '{"queries":["undefined"],"maxResultsPerQuery":50}'

🚀 Getting Started (3 steps)

1. Choose your targets — protocol names or chains.
2. Set the cap — maxResultsPerQuery limits rows per query.
3. Run and export — get a clean dataset as JSON, CSV or Excel.

📥 Input

{"queries":["undefined"],"maxResultsPerQuery":50}

Field	Type	Description
queries	array	Protocol names or chains.
maxResultsPerQuery	integer	Caps rows per query.
maxConcurrency	integer	How many queries to fetch at once.
includeRaw	boolean	Attach the source’s untouched record under raw.

📤 Output

One row per company, saved to the dataset. Every row also carries query, scrapedAt, and — when a lookup fails — an error explaining why (never silently dropped, never billed).

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({"queries":["undefined"],"maxResultsPerQuery":50});
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={"queries":["undefined"],"maxResultsPerQuery":50})
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 queries → 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 maxResultsPerQuery, or refine the name.
• 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 — 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.