Stats
Check usage, confirmed token and funding figures, markets and holder rewards.
Stats shows how much Deference is used, observed token and funding figures, markets, and holder rewards. It is public and needs no account.
The page has four sections: Usage, Funding, Markets and Holder rewards. Markets appears only on networks where the order book is deployed. Each names its source and window under its heading. In Usage, choose a range, then use the chart's menu to select Requests, Tokens, or Credit spent. View data opens the chart's values as a table. Contracts, beside Funding, lists the contract addresses to copy or open in the explorer, and the confirmed block the chain figures were read at.
Where the numbers come from
| Kind | Source | Refreshed |
|---|---|---|
| On chain | The INFERENCE token, the sale, the DEF token and its hook, read together at one confirmed block | Every 60 seconds |
| Order book | Placements, fills, cancellations, and claims indexed from the book contract, where one is deployed | As new blocks are indexed |
| Usage | Hourly totals of API requests | Every 5 minutes |
| Reported | Finalized credit spend recorded by Deference | With the network snapshot |
Times are in UTC. Refresh the page for the latest figures. A missing figure is unknown. A displayed zero is an observed zero.
How we measure, Data (JSON), and Service status are icon links beside the page title. The Data (JSON) tooltip says "Network data as JSON". Contracts names the chain figures as "read at confirmed block N".
Chain figures say "On chain" at that block, or "On chain at block N" for a different one. The order book adds "Read at block N" when its read differs.
Usage names the days its hourly totals cover. When those totals fall behind, the chart ends on their last day. The JSON's meta.measured gives the same interval. The JSON names the network, the indexed block behind the order book figures, and whether the index is behind or rebuilding.
Funding
| Figure | Meaning | Source |
|---|---|---|
| Funding wallet | The observed USDC balance of the sale's funding wallet | On chain |
| Circulating supply | The token's total supply of INFERENCE at the confirmed block | On chain |
| Credit activated | Spendable service credit after activation fees, all time | Confirmed activation receipts |
| Purchased credit used | Finalized paid service credit spent on requests, all time. Usage's credit spent also counts free credit, so it can be higher | Recorded by Deference |
The funding wallet receives sale proceeds. Its balance is an observation of that wallet, not an enforceable reserve obligation. The page does not calculate a funding ratio against tokens or unused credit.
Amounts are rounded for display; the JSON retains integer base units. Contracts names the confirmed block and links to these measurement details.
Usage
The Usage chart draws requests, tokens or credit spent per UTC day. Success rate and median time to first token appear for the selected range.
| Figure | Meaning |
|---|---|
| Requests | Recorded requests that have finished, including failures |
| Tokens | Input and output tokens of succeeded requests, as each provider counts them |
| Credit spent | The cost of completed requests, including eligible free credit |
| Success rate | The share of counted requests that did not fail |
| Median time to first token | Median time to the first token for succeeded streamed requests |
A request failed when it ended with a 5xx, a provider 408 or 429, an error inside a stream, a broken stream, or an unreachable provider. Requests abandoned for 15 minutes also count as failures. A 400, 401, 402, 403, 404, 413 or 422 rejects the caller's request and is excluded from those rates. Rates and percentiles appear from 20 requests.
Status shows whether each part of Deference is working.
Models
The All N models link in Top models shows the catalog size when that count is available.
Top models lists models with the most tokens in the selected Usage range. Choose 7d, 30d, or All time. The default is 30d. The line above the rankings names the days they cover. When the two tables cover different days, each names its own.
A model is named only after at least 50 requests from at least 5 accounts. The list appears once three models qualify. The rest is summed into Other. Top clients also ranks by tokens and folds entries below the request and account thresholds.
Order book
Where the order book is deployed, the Markets section shows it. The book holds asks only, so it has a best price but no spread.
The Order book ladder lists Price (USDC) and Listed INFERENCE, highest price first. Last trade appears when a recent fill is available.
Listing prices run from 0.50 to 1.00 USDC in steps of 0.05. Listings have no expiry. Cancelled and fully filled amounts are excluded from active liquidity.
External-volume totals in the order book stats JSON exclude self fills and routed fills whose paying wallet has not been attributed. Order book on Home's Sell view shows every price from 0.50 to 1.00 USDC.
Use the Buy INFERENCE quote on Home for executable output. See Order book for matching and limits, and Selling to list INFERENCE.
Rewards
Holder rewards lists the newest flushes of the DEF pool's fees, the same rows Rewards prints, and View rewards leads to the full flush history there. On a chain without the DEF program the panel shows Payout history is not available yet.
The network JSON still carries the program's totals, read at the confirmed block.
| Field | Meaning | Source |
|---|---|---|
rewardsFunded, rewardsAllocated | INFERENCE paid into the DEF token's books, all time. Both carry totalRewarded, because DEF allocates on payment | On chain |
rewardsPending | The INFERENCE a flush would pay holders now | A simulation of the flush |
pendingWeth | The ETH fee waiting in the pool | The same simulation |
rewards.epochs | Flushes of the pool's fees | Indexed Flushed events |
rewards.harvested, rewards.claimed | INFERENCE paid in and claimed out, from the indexed token events | Indexed RewardNotified and Claimed events |
See Rewards for eligibility, claims and how to check a payout.