GET /v1/leaderboards/deployers

​

Endpoint

GET /v1/leaderboards/deployers

​

Query parameters

​

Response (current — feature pending)

{
  "ranked_by": "revenue",
  "count": 0,
  "deployers": [],
  "note": "HIP-4 deployer fee rate is currently 0 across all markets — Hyperliquid has not activated deployer revenue on-chain yet. This endpoint will populate automatically once HL deployers start earning fees. Builder fees (separate mechanism) are tracked at /v1/leaderboards/builders.",
  "feature_status": "pending_upstream"
}

​

Response (future — when HL activates deployer fees)

{
  "ranked_by": "revenue",
  "count": 1,
  "deployers": [
    {
      "rank": 1,
      "outcome_id": 0,
      "title": "BTC >= $78213 by 2026-05-03 06:00 UTC (1d)",
      "outcome_name": "Recurring",
      "underlying": "BTC",
      "target_price": "78213",
      "fills_count": 26732,
      "volume_usdh": "1147289.829980",
      "deployer_fees_total_usdh": "147.32",
      "effective_bps": "1.28",
      "distinct_fee_tokens": 1,
      "first_trade": { "us": 1777719604322000, "iso": "...", "relative": "7h ago" },
      "last_trade":  { "us": 1777743859009000, "iso": "...", "relative": "51m ago" }
    }
  ],
  "feature_status": "live"
}

​

Ranking modes

• by=revenue — deployer_fees_total DESC. Default.
• by=volume — outcomes with biggest USDH volume regardless of deployer fee.
• by=bps — outcomes with the highest effective deployer rate. Useful for finding outliers.

​

Use cases

• Market-creator earnings dashboard for HL teams running price-binary deployments.
• Find outliers — outcomes with effective_bps > 50 are charging unusually high deployer fees.
• Volume vs revenue analysis — sort by volume, look at the bps column to see who’s monetizing aggressively.

​

Examples

curl -H "X-API-Key: hip4_live_..." \
  "https://hip4.polynode.dev/api/v1/leaderboards/deployers?limit=50"

# Highest effective rate
curl -H "X-API-Key: hip4_live_..." \
  "https://hip4.polynode.dev/api/v1/leaderboards/deployers?by=bps&limit=10"

import requests
r = requests.get("https://.../api/v1/leaderboards/deployers",
                 headers={"X-API-Key": key},
                 params={"by": "revenue"}).json()
for d in r["deployers"][:10]:
    print(f"#{d['rank']:>2} oid={d['outcome_id']:>4} "
          f"vol=${d['volume_usdh']}  fees=${d['deployer_fees_total_usdh']}  "
          f"bps={d['effective_bps']}  {d['title'][:50]}")

​

Notes

• Currently empty across the board — see callout at top. Builder fees (active) are tracked at /v1/leaderboards/builders.
• distinct_fee_tokens > 1 will mean the deployer has been collecting fees in different tokens across fills (e.g. some in USDH, some in share-side tokens).
• The deployer-of-an-outcome address is not exposed in current state — this endpoint groups by outcome_id, not by deployer address. Cross-outcome aggregation will arrive in a future schema update.

​

How to know when this goes live