DeFi protocol fees and revenue

Protocols ranked by fees paid by users (or by protocol revenue with metric "revenue") over the last 24h from DefiLlama's free fees overview: per-protocol 24h/7d/30d/1y/all-time totals with 1d/7d/30d change, category and chains; optional chain scope, category filter and name search; chain-level rows (network gas fees) via type "chain"; sector totals. limit up to 100. Send POST /api/defi-fees with no required fields (6 optional) and pay $0.002 per call over x402 or MPP (there is no free tier). It returns a JSON object with source, fetchedAt, cached, metric, unit and 6 more.

Keyless public data.

Category: Crypto & onchain data · Tags: crypto defi fees revenue protocols ranking defillama

TRY IN PLAYGROUND →

Parameters

Example request

curl -i -X POST https://agent402.tools/api/defi-fees \
  -H "Content-Type: application/json" \
  -d '{"metric":"fees","limit":5}'

Without payment this returns HTTP 402 Payment Required with the exact price for defi-fees; any x402 v2 or MPP client pays it and retries.

Example response

{
  "source": "defillama-fees",
  "fetchedAt": "2026-08-22T12:00:00.000Z",
  "cached": true,
  "metric": "fees",
  "unit": "USD",
  "chain": null,
  "totals": {
    "total24hUsd": 75393517,
    "total7dUsd": 423480844,
    "total30dUsd": 1800000000,
    "change1dPct": 6.68,
    "change7dPct": 2.1,
    "change1mPct": 10.2
  },
  "chains": [
    "Solana",
    "Ethereum",
    "Base"
  ],
  "matched": 2500,
  "count": 1,
  "protocols": [
    {
      "rank": 1,
      "name": "Tether",
      "slug": "tether",
      "category": "Stablecoin Issuer",
      "protocolType": "protocol",
      "chains": [
        "Ethereum"
      ],
      "chainCount": 1,
      "total24hUsd": 15900806,
      "total7dUsd": 111368600,
      "total30dUsd": 481404902,
      "total1yUsd": 5800000000,
      "totalAllTimeUsd": 20000000000,
      "change1dPct": 0,
      "change7dPct": -0.03,
      "change1mPct": 1.2
    }
  ]
}

From an MCP client

catalog.call {
  "slug": "defi-fees",
  "params": {
    "metric": "fees",
    "limit": 5
  }
}

The hosted connector at https://agent402.tools/mcp needs a payment for defi-fees; the stdio package pays it from a wallet or from AGENT402_CREDITS_KEY. Local install: npx -y agent402-mcp.

Errors and behavior

• Every field is optional. An input the tool rejects returns an HTTP 4xx whose body carries error, tool, expected, required and example.
• A paid call that ends in any status of 400 or above is not charged over x402, MPP or a prepaid credits key: settlement is cancelled when the tool fails. The exception is a Tempo push credential, a transfer the buyer sent before the call: it settles before the tool runs, so if the tool then fails the payment is recorded as a refund owed to the paying wallet.
• Wallet-only: this tool reaches the network or stored state, so it has no proof-of-work tier. A prepaid card-credits key issued earlier (Authorization: Bearer a402_...) also pays it.
• A GET or HEAD to /api/defi-fees returns the same 402 quote, so the price can be read without a body.
• An Idempotency-Key header makes a retried paid call replay the first 200 instead of charging again (an answer larger than 1 MB is not replayed).

Paid call (JavaScript agent)

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client();
client.setSpendControls?.(false); // keep your own spending ceiling in code
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);

const res = await payFetch("https://agent402.tools/api/defi-fees", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    "metric": "fees",
    "limit": 5
  }),
});

Related tools