Token utilisation report

no batch stored yet

Disclaimer: This site is for informational purposes only. Model rankings, usage data, pricing, capabilities and hardware results change frequently and may vary by benchmark, provider and workload. Verify current source data, licensing, security, privacy, compliance and deployment requirements before making production or purchasing decisions.

Tokens in view
0
Model rows
0
Countries
0
Category slices
24

KPI dashboard

for the selected category and filters

Top model
—
— of slice tokens
Avg weekly growth
—
mean across models in view
Leading country
—
— share · 0 models
Developers
0
distinct model makers

Data quality

Checks passed

Coverage

  • 0/24 categories collected
  • 0 rows · 0 models
  • 0 developers · 0 countries

Week covered

  • no batch stored yet
  • collected —
  • trailing-week totals per source feed

Consistency checks

  • Token shares sum to ~100% in every category
  • No duplicate model rows per category
  • 0 rows without a prior week · 0 rows with unmapped country
CategoryRowsShare sumStatus
No data collected yet — run “Refresh tokens”.

Tokens processed by model

Tokens by developer country

Country drill-down

CountryTokensShareModels
No token data yet — run “Refresh tokens”.

Granular model rows

#ModelDeveloperCountryCategoryTokensShareWeekly growth
Nothing to show for these filters.

KPI definitions

  • Tokens processed — Total tokens routed through the source in the trailing window.
  • Token share — Model's share of all tokens captured in the same slice.
  • Weekly growth — Change in tokens processed versus the previous window.
  • Country token share — Share of tokens attributed to the model developer's home country.
  • Models per country — Distinct models from that country present in the captured slices.

Collection rules

  • Only live, openly reachable endpoints - no periodic report or PDF sources.
  • Refresh token utilisation in the same run as the primary leaderboard refresh.
  • Attribute country by model developer origin; unknown developers fall back to Unspecified.
  • Always keep raw token counts alongside derived share and growth KPIs.

Sources