Nostr Ecosystem Metrics over MCP

Size of the curated Routstr model catalog over time - one row per archived version of the curated key's kind-38423 (routstr-model-catalog) 'routstr-21-models' list, the Models tab's 'Catalog size over time' line. A level, not a flow: values are NOT additive across rows; the last row is the current catalog size.

Cumulative observed Routstr revenue in millisats - the running total of everything included providers have reported earning, the Overview tab's 'Cumulative observed revenue' line; the final row equals the page's all-time revenue headline. A running total, so values are NOT additive across rows.

Per-model Routstr activity over included providers - reported revenue (msats), successful requests and tokens per model identifier, at grain=day one row per (bucket, model), at grain=total one row per model summed over the from/to window (omit both for all time). The data behind the Models tab's 'Daily revenue by model' chart, served for EVERY model rather than the chart's top-6 fold.

Every model served on Routstr with its 30d and all-time reported revenue, requests, tokens and 30d provider count - the Models tab table of dev.nostrolo.gy/routstr, one row per model identifier, ranked by 30d revenue with '(other)' last. A CURRENT-STATE snapshot: no time axis, never sum across calls; for a caller-chosen window use routstr.model_activity.

The Routstr network's daily activity - revenue (msats), successful requests, tokens and active providers per UTC day - exactly the series behind the dev.nostrolo.gy/routstr Overview charts. Counts network activity, not distinct users (Routstr publishes no user-side events).

The Routstr headline figures in ONE row - the four cards at the top of dev.nostrolo.gy/routstr plus the coverage dates and the exclusion ledger counts. A snapshot of the newest refresh, not a time series: no day axis, and nothing here is additive across calls.

Per-provider Routstr activity from the reconstructed ledger - reported revenue (msats), successful requests and tokens per provider, at grain=day one row per (bucket, provider), at grain=total one row per provider summed over the from/to window (omit both for all time). This is the data behind the Providers tab's 'Daily revenue by provider' chart, served for EVERY included provider rather than the chart's top-20 fold.

How the ANNOUNCED Routstr network is shaped - providers by endpoint class (clearnet/onion/both/private-only/none), by announced software version, and by accepted Cashu mint host - the three Network tab breakdowns, one row per (facet, value). Counts announcements, not usage.

Every Routstr provider with its 30d and all-time reported revenue, requests and tokens plus its registry facts (endpoint class, version, curation label, first/last seen) - the Providers tab of dev.nostrolo.gy/routstr, one row per provider pubkey, ranked by all-time revenue. A CURRENT-STATE snapshot: no time axis, never sum across calls; for a caller-chosen window use routstr.provider_activity.

The Routstr network's self-reported request success rate over the trailing 30 days - the Network tab's 'Reliability, as reported' figures, one row. A snapshot, not a series.