# Protocol Revenue Leaderboard (`gochujang/protocol-revenue-leaderboard`) Actor

Track DeFi protocol fee revenue rankings with daily, weekly, monthly breakdowns and growth trends

- **URL**: https://apify.com/gochujang/protocol-revenue-leaderboard.md
- **Developed by:** [Hojun Lee](https://apify.com/gochujang) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 item processeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### What does Protocol Revenue Leaderboard do?

**Protocol Revenue Leaderboard** fetches real-time **DeFi protocol fee and revenue data** from DeFiLlama and ranks every protocol by earnings across multiple timeframes — 24h, 7d, 30d, and 1y. It enriches each entry with **momentum scores, revenue trend classification, consistency ratings, and annualised run-rate tiers** so you can instantly identify which protocols are growing, declining, or generating the most sustainable on-chain revenue. Run it on a schedule with the Apify platform to power dashboards, alerts, and investment research pipelines without managing any infrastructure.

### Why use Protocol Revenue Leaderboard?

- **Up-to-date DeFi revenue rankings** — pulls directly from DeFiLlama's fees endpoint, covering hundreds of protocols across DEXes, lending markets, derivatives, and more; no manual data collection needed.
- **Multi-timeframe momentum analysis** — computes a weighted momentum score (50% 1d, 30% 7d, 20% 1m) alongside a revenue acceleration metric so you can spot protocols gaining or losing traction before the broader market reacts.
- **Revenue consistency scoring** — calculates a 0–100 consistency score from daily chart data so you can distinguish genuine sustainable earners from one-day fee spikes.
- **Category-level benchmarking** — assigns category ranks (e.g. rank 2 among all Lending protocols) alongside global rank, letting you compare apples to apples across protocol types.
- **Structured, API-ready output** — every record follows a clean JSON schema that drops straight into Google Sheets, BigQuery, Databricks, or any BI tool via Apify's dataset export API.

### How to use Protocol Revenue Leaderboard

1. Go to the [Apify Store](https://apify.com/store) and search for **Protocol Revenue Leaderboard**.
2. Click **Try for free** to open the Actor input form.
3. Set **Top N** (default 50) to control how many protocols you want returned.
4. Optionally enter a **Minimum 24h Revenue** threshold in USD to filter out dust-level protocols.
5. Use the **Categories** field to narrow results to specific protocol types such as `Dexes`, `Lending`, or `Derivatives`. Leave empty to fetch all.
6. Choose a **Sort By** field: `total24h`, `total7d`, `total30d`, `total1y`, `change_1d`, or `change_7d`.
7. Click **Start** and wait a few seconds for the run to complete.
8. Download your dataset as JSON, CSV, or Excel from the **Dataset** tab, or integrate via the Apify API.

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `top_n` | integer | 50 | Number of top protocols to return (max 200) |
| `min_revenue_24h_usd` | integer | 10000 | Minimum 24-hour fee revenue in USD to include a protocol |
| `categories` | array | \[] | Filter by protocol category (e.g. `Dexes`, `Lending`, `Derivatives`). Empty = all |
| `sort_by` | string | `total24h` | Sort field: `total24h`, `total7d`, `total30d`, `total1y`, `change_1d`, `change_7d` |

### Output

```json
[
  {
    "rank": 1,
    "name": "uniswap-v3",
    "display_name": "Uniswap V3",
    "category": "Dexes",
    "chains": ["Ethereum", "Arbitrum", "Polygon", "Optimism"],
    "chain_count": 4,
    "revenue_24h_usd": 1842300.50,
    "revenue_7d_usd": 11920400.00,
    "revenue_30d_usd": 48310000.00,
    "revenue_1y_usd": 620000000.00,
    "change_1d_pct": 12.4,
    "change_7d_pct": 8.1,
    "change_1m_pct": -3.2,
    "revenue_run_rate_annualized": 579720000.00,
    "revenue_efficiency_tier": "unicorn",
    "revenue_trend": "growing",
    "revenue_momentum_score": 9.73,
    "revenue_acceleration": 4.3,
    "revenue_per_chain_30d": 12077500.00,
    "daily_to_weekly_revenue_pct": 15.46,
    "revenue_consistency_score": 84.2,
    "revenue_volatility_class": "low",
    "category_rank": 1
  },
  {
    "rank": 2,
    "name": "aave-v3",
    "display_name": "Aave V3",
    "category": "Lending",
    "chains": ["Ethereum", "Polygon", "Avalanche"],
    "chain_count": 3,
    "revenue_24h_usd": 890150.00,
    "revenue_7d_usd": 5820000.00,
    "revenue_30d_usd": 23100000.00,
    "revenue_1y_usd": 290000000.00,
    "change_1d_pct": 4.7,
    "change_7d_pct": 2.3,
    "change_1m_pct": 6.1,
    "revenue_run_rate_annualized": 277200000.00,
    "revenue_efficiency_tier": "unicorn",
    "revenue_trend": "stable",
    "revenue_momentum_score": 3.91,
    "revenue_acceleration": 2.4,
    "revenue_per_chain_30d": 7700000.00,
    "daily_to_weekly_revenue_pct": 15.29,
    "revenue_consistency_score": 77.6,
    "revenue_volatility_class": "low",
    "category_rank": 1
  }
]
```

### Data fields

| Field | Description |
|-------|-------------|
| `rank` | Overall rank by chosen sort field (1 = highest) |
| `name` | Protocol slug used by DeFiLlama |
| `display_name` | Human-readable protocol name |
| `category` | Protocol category (e.g. Dexes, Lending, Derivatives) |
| `chains` | List of blockchain networks the protocol operates on |
| `chain_count` | Number of chains |
| `revenue_24h_usd` | Protocol fees collected in the last 24 hours (USD) |
| `revenue_7d_usd` | Fees collected in the last 7 days (USD) |
| `revenue_30d_usd` | Fees collected in the last 30 days (USD) |
| `revenue_1y_usd` | Fees collected in the last year (USD) |
| `change_1d_pct` | Percentage change vs. prior 24-hour window |
| `change_7d_pct` | Percentage change vs. prior 7-day window |
| `change_1m_pct` | Percentage change vs. prior 30-day window |
| `revenue_run_rate_annualized` | 30d revenue × 12 — annualised projection (USD) |
| `revenue_efficiency_tier` | Tier label: `unicorn` ($1B+), `major`, `mid`, `emerging`, `micro` |
| `revenue_trend` | `growing`, `stable`, or `declining` based on 7d change |
| `revenue_momentum_score` | Weighted composite score from 1d/7d/1m changes (−100 to +100) |
| `revenue_acceleration` | 1d change minus 7d change — positive = short-term acceleration |
| `revenue_per_chain_30d` | 30d revenue divided by chain count — efficiency metric |
| `daily_to_weekly_revenue_pct` | Last 24h revenue as a percentage of 7d revenue |
| `revenue_consistency_score` | 0–100 score; higher = more consistent daily revenue |
| `revenue_volatility_class` | `low`, `medium`, or `high` based on consistency score |
| `category_rank` | Rank within the protocol's own category |

### Cost estimation

Pricing is **Pay-Per-Event** at **$0.001 per protocol tracked**.

| Scenario | Protocols | Estimated cost |
|----------|-----------|----------------|
| Small — top 10 protocols | 10 | $0.01 |
| Medium — top 50 protocols (default) | 50 | $0.05 |
| Large — top 200 protocols | 200 | $0.20 |

Running once daily for a full month costs under $1.50 even at maximum scale. The DeFiLlama API is free and public, so there are no upstream data costs.

### FAQ

**Q: Where does the data come from?**
A: All revenue data is sourced from the [DeFiLlama fees API](https://api.llama.fi/overview/fees), which aggregates on-chain fee data from protocol subgraphs and smart contract events. DeFiLlama data is widely regarded as the most comprehensive public DeFi analytics source.

**Q: How often should I run this Actor?**
A: DeFiLlama updates its fees data every few hours. Running the Actor once or twice per day is sufficient for most research and monitoring use cases. Use Apify's built-in scheduler to automate runs without writing any code.

**Q: Can I filter to just one blockchain ecosystem?**
A: The current version filters by protocol category (e.g. Dexes, Lending). Chain-level filtering can be applied post-collection by filtering the `chains` array field. Category filtering combined with the sort options covers the vast majority of analytical workflows.

This Actor retrieves publicly available data from DeFiLlama's open API. It does not access private or user-specific DeFi data. Protocol revenue figures represent fees paid by users and may differ from protocol treasury revenue depending on fee-sharing configurations. Always validate data against primary sources before making investment decisions.

Keywords: DeFi protocol revenue, DeFiLlama scraper, on-chain fee tracker, crypto protocol ranking, DeFi analytics, protocol earnings data, DEX revenue, lending protocol fees, DeFi leaderboard, blockchain revenue API

***

### Related actors

- [DeFi Fee Revenue Ranker](https://apify.com/gochujang/defi-fee-revenue-ranker) — Daily fee breakdown with 30+ computed analytics to complement this actor's leaderboard
- [DeFi TVL Velocity Ranker](https://apify.com/gochujang/defi-tvl-velocity-ranker) — TVL momentum alongside revenue for identifying protocols gaining ground
- [DeFi Risk Dashboard](https://apify.com/gochujang/defi-risk-dashboard) — Protocol risk scores to filter the revenue leaderboard by safety tier

### Feedback

If this actor powers your DeFi analytics, a review helps others find it: [Leave a review on Apify Store](https://apify.com/gochujang/protocol-revenue-leaderboard#reviews)

# Actor input Schema

## `top_n` (type: `integer`):

Number of top protocols to return

## `min_revenue_24h_usd` (type: `integer`):

Minimum 24h fees to include

## `categories` (type: `array`):

Filter by protocol category (e.g. Dexes, Lending, Derivatives). Empty = all.

## `sort_by` (type: `string`):

Sort field

## Actor input object example

```json
{
  "top_n": 50,
  "min_revenue_24h_usd": 10000,
  "categories": [],
  "sort_by": "total24h"
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("gochujang/protocol-revenue-leaderboard").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("gochujang/protocol-revenue-leaderboard").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call gochujang/protocol-revenue-leaderboard --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,gochujang/protocol-revenue-leaderboard"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/XlKvLXEgEbvDgw8dS/builds/c0x6DgcLx0enlsgND/openapi.json