Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.codex.io/llms.txt

Use this file to discover all available pages before exploring further.

Global Fees Paid (GFP) is a unified view of every dollar of fees a token, pool, or trader generates, broken into five components, summed into a single total, and combined into a handful of derived metrics. The same five components appear across bar queries, token filters, event feeds, and launchpad subscriptions, so once you understand them here you’ll recognize them everywhere they’re surfaced.

​
What Global Fees Paid measures

GFP captures the full economic cost of activity on-chain. Not just the trading fee a pool charges, but everything paid to network validators, block builders, and (on rollups) the L1 chain that posts the data. Every field is denominated in USD and summed at the start of the query window.The five components are the same on every endpoint. What changes is the shape of the data: a single scalar per event, an array per bar, a pre-computed value over a time window, or a single-window snapshot. The endpoint coverage map below shows which shape you get where.

​
Endpoint coverage

This is the master map. Find the endpoint you’re using and follow the link to see the fields it exposes.
EndpointType returnedField set
getTokenEventsEvent (with feeData)Per-transaction fee detail
getTokenEventsForMakerEvent (with feeData)Per-transaction fee detail
onEventsCreatedByMakerEvent (with feeData)Per-transaction fee detail
getBarsBarsResponseChart queries
getTokenBarsTokenBarsResponseChart queries
onBarsUpdatedIndividualBarDataChart subscriptions
onTokenBarsUpdatedIndividualBarDataChart subscriptions
filterTokensTokenFilterResultToken filtering
onFilterTokensUpdatedTokenFilterResultToken filtering
onLaunchpadTokenEventLaunchpadTokenEventOutputLaunchpad subscriptions
onLaunchpadTokenEventBatchLaunchpadTokenEventOutputLaunchpad subscriptions

​
The five components

All five components are USD-denominated everywhere they appear in the schema. Some endpoints additionally expose the underlying native-unit values (wei on EVM, lamports on Solana). See per-transaction fee detail for that.
ComponentWhat it measures
poolFeesDEX/pool fees collected by the pool itself. The “trading fee,” typically distributed to liquidity providers and/or the protocol.
baseFeesBase fees paid to the network as gas. On EVM this is baseFeePerGas × gasUsed; on Solana it’s roughly 5000 lamports × signature count.
priorityFeesPriority/tip portion of gas, paid to validators. EIP-1559 priority fee on EVM; tip portion of total fee on Solana.
builderTipsDirect payments to block builders. The cleanest on-chain MEV signal: ETH transfers to block.coinbase on EVM, Jito tips on Solana.
l1DataFeesCost of posting rollup data to L1. L2-only (Base, Optimism, Arbitrum, etc.). Always 0 on L1s and Solana.

​
Derived metrics

Built from the five components, these surface the most common questions developers ask about fee data without making them do the arithmetic.
FieldFormulaWhat it tells you
totalFeespoolFees + baseFees + priorityFees + builderTips + l1DataFeesTotal economic cost over the window.
feeToVolumeRatiototalFees / volumeNormalized fee burden: how expensive activity is relative to volume.
mevToTotalFeesRatiobuilderTips / totalFeesShare of activity going to block builders. Your MEV-exposure indicator.
gasPerVolume(baseFees + priorityFees + l1DataFees) / volumePure gas cost per dollar of volume, excluding pool and builder fees.
averageCostPerTradetotalFees / transactionsAverage user cost per trade in USD.
Ratios are null when their divisor is zero (no volume, no transactions, or no total fees). Always handle the null case in client code.

​
Classifications

Two categorical fields summarize the fee profile at a glance, useful for filtering, alerting, or labeling tokens in a UI without surfacing raw numbers.mevRiskLevel, based on mevToTotalFeesRatio:
  • low: builder tips are less than 3% of total fees
  • medium: between 3% and 30%
  • high: more than 30%
  • null: when totalFees is zero
feeRegimeClassification describes which fee component dominates:
  • gas-dominated: gas (base + priority + L1 data) is more than 50% of fees
  • mev-dominated: builder tips are more than 20% of fees
  • pool-fee-dominated: pool fees dominate
  • null: when fees are zero

​
Caveats and gotchas

A few things that are easy to miss and worth flagging up front:
  • Subscriptions only expose the five raw components. IndividualBarData (used by onBarsUpdated and onTokenBarsUpdated) does not include derived metrics or classifications. If you need totalFees or any ratio in a streaming context, compute it client-side or pull it from the corresponding query.
  • Launchpad feeToVolumeRatio1 is a Float, not a String. Everywhere else in the schema, ratio fields are returned as strings (to preserve precision on very small or very large values). On LaunchpadTokenEventOutput it’s a float. Your parsing layer needs to handle both.
  • Filter inputs are a subset of result fields. filterTokens returns 35 fee fields, but only seven of them are usable as filter inputs. The full list is in the token filtering section.
  • Component-level filters at shorter windows aren’t accepted as filter inputs. You can filter on totalFees5m but not builderTips5m. Component-level filters are only available for the 24h window (poolFees24).
  • Native-unit fields are chain-specific. On EventFeeData, fields like baseFeeNativeUnit are wei on EVM and lamports on Solana: same field name, different units. The USD-denominated parent fields don’t have this ambiguity.

​
Per-transaction fee detail

Every event returned by an event-feed endpoint carries a feeData object with both the USD-denominated GFP components and native-unit raw values. This is the most granular fee data the API exposes: one record per swap.USD components (same definitions as above): poolFees, baseFees, priorityFees, builderTips, l1DataFees, totalFees.Pool-fee detail:
FieldTypeMeaning
poolFeeRateRawStringPool fee rate in the protocol’s native encoding (e.g. raw uint24 for Uniswap V3).
poolFeeBpsFloatPool fee rate normalized to basis points (1 bps = 0.01%).
poolFeeAmountRawStringPool fee absolute amount in the fee token’s smallest unit, when known per-swap.
dynamicFeeBooleantrue when the pool fee is dynamic (Uniswap V4 hooks, AlgebraIntegral plugins).
estimatedPoolFeeBooleantrue when poolFeeBps is a protocol-level estimate rather than an exact per-swap value.
Native-unit gas detail (wei on EVM, lamports on Solana):
FieldTypeMeaning
baseFeeNativeUnitStringBase fee portion of gas. On EVM: baseFeePerGas × gasUsed. On Solana: 5000 × signatures.
priorityFeeNativeUnitStringPriority fee. On EVM: (effectiveGasPrice − baseFeePerGas) × gasUsed. On Solana: meta.fee − baseFee.
gasUsedStringGas units (EVM) or compute units (Solana) consumed by the transaction.
builderTipNativeUnitStringDirect payment to the block builder. ETH transfers to block.coinbase on EVM, Jito tip on Solana.
l1DataFeeNativeUnitStringL1 data posting fee (L2 rollups only).
txEventCountIntNumber of DEX events in the transaction. Use this as the divisor for pro-rating tx-level fees per event.
Supplemental fee data: EventFeeData.supplementalFeeData is a union type carrying protocol-specific fields. It currently has two variants, both for Pump.fun cashback:
  • PumpCashbackFeeData for Pump V1 swaps. Fields: type (always "PumpCashback"), cashbackFeeBps, cashbackAmountLamports.
  • PumpAmmCashbackFeeData for Pump AMM swaps. Same field shape, with type = "PumpAmmCashback".
The maker/wallet endpoints (getTokenEventsForMaker, onEventsCreatedByMaker) are the simplest path to per-transaction fee detail for a specific wallet. Useful for trader analytics, MEV exposure tracking, or PnL accounting that includes gas costs.

​
Chart queries

getBars and getTokenBars return parallel arrays. The value at index i corresponds to the bar starting at timestamp t[i]. All twelve fields are exposed: the five components, totalFees, the four ratios, and both classifications.
FieldTypeNotes
poolFees[String]USD per bar.
baseFees[String]USD per bar.
priorityFees[String]USD per bar.
builderTips[String]USD per bar.
l1DataFees[String]USD per bar. Always 0 outside L2 rollups.
totalFees[String]USD per bar.
feeToVolumeRatio[String]Null when bar volume is zero.
mevToTotalFeesRatio[String]Null when totalFees is zero.
gasPerVolume[String]Null when volume is zero.
averageCostPerTrade[String]Null when no transactions.
mevRiskLevel[String]Per-bar enum: low / medium / high, or null.
feeRegimeClassification[String]Per-bar enum: gas-dominated / mev-dominated / pool-fee-dominated, or null.

​
Chart subscriptions

onBarsUpdated and onTokenBarsUpdated deliver one bar update at a time, so each fee field is a single scalar rather than an array. Only the five raw components are exposed here. Derived metrics and classifications are not.
FieldTypeMeaning
poolFeesStringUSD for this bar.
baseFeesStringUSD for this bar.
priorityFeesStringUSD for this bar.
builderTipsStringUSD for this bar.
l1DataFeesStringUSD for this bar.
IndividualBarData is nested inside OnBarsUpdatedResponse.aggregates.{r1, r5, r15, r60, …}.{usd, token}. Resolution and currency are picked at the wrapper level, then the bar’s fields are fetched.
If you need totalFees, mevRiskLevel, or any ratio in a subscription context, compute it client-side from the five components or pull it from getBars / getTokenBars.

​
Token filtering

filterTokens and onFilterTokensUpdated return per-token results with fees pre-computed across five rolling windows ending at “now”: 5 minutes, 1 hour, 4 hours, 12 hours, and 24 hours. Each window suffix gives you a different field name.Seven fields × five windows = 35 fee-related fields per token. The base names are:
  • poolFees{w}, baseFees{w}, priorityFees{w}, builderTips{w}, l1DataFees{w}: the five components
  • totalFees{w}: the sum
  • feeToVolumeRatio{w}: the ratio
Where {w} is one of 5m, 1, 4, 12, 24. So the fully-enumerated set includes poolFees5m, poolFees1, poolFees4, poolFees12, poolFees24, baseFees5m, …, feeToVolumeRatio24.

​
Filter inputs

The TokenFilters input accepts a subset of the result fields. Only seven inputs are filterable:
Filter inputTypeNotes
totalFees5mNumberFiltergt / lt / between against summed fees over 5 minutes.
totalFees1NumberFilter…over 1 hour.
totalFees4NumberFilter…over 4 hours.
totalFees12NumberFilter…over 12 hours.
totalFees24NumberFilter…over 24 hours.
poolFees24NumberFilterThe only component-level filter: 24h pool fees.
feeToVolumeRatio24NumberFilter24h ratio filter.
Component-level filters at shorter windows (e.g. builderTips24, baseFees1) are not accepted as filter inputs.

​
Ranking attributes

All 35 result fields are usable as ranking.attribute values for sorting:
poolFees5m, poolFees1, poolFees4, poolFees12, poolFees24,
baseFees5m, baseFees1, baseFees4, baseFees12, baseFees24,
priorityFees5m, priorityFees1, priorityFees4, priorityFees12, priorityFees24,
builderTips5m, builderTips1, builderTips4, builderTips12, builderTips24,
l1DataFees5m, l1DataFees1, l1DataFees4, l1DataFees12, l1DataFees24,
totalFees5m, totalFees1, totalFees4, totalFees12, totalFees24,
feeToVolumeRatio5m, feeToVolumeRatio1, feeToVolumeRatio4, feeToVolumeRatio12, feeToVolumeRatio24

​
Launchpad subscriptions

onLaunchpadTokenEvent and onLaunchpadTokenEventBatch deliver real-time updates on launchpad tokens (Pump.fun, Bonk, MeteoraDBC, Pump Mayhem, etc.). Fee fields populate on eventType: "Updated" events; other event types (Deployed, Created, Migrated, Completed, and the Unconfirmed* variants) carry the field shape but values may be null.Only the 1-hour window is exposed:
FieldTypeNotes
poolFees1StringUSD over the last hour.
baseFees1StringUSD over the last hour.
priorityFees1StringUSD over the last hour.
builderTips1StringUSD over the last hour.
l1DataFees1StringUSD over the last hour. Always 0 for non-L2 launchpad networks (most of them).
totalFees1StringSum of the five components, USD.
feeToVolumeRatio1FloattotalFees1 / volume1. Note: this is a Float, unlike the String ratios elsewhere in the schema.
onLaunchpadTokenEventBatch is the more efficient choice when you don’t need event-by-event delivery. It returns batched arrays in a single message.