Metrics / routstr / catalog_size
catalog_size
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.
unit
models
grain
day (UTC)
series
sparse, full history
key
routstr.catalog_size@day
Parameters
| param | accepted values |
|---|---|
| grain | day - default day (omit to get the default) |
| from | optional inclusive ISO UTC calendar day (YYYY-MM-DD); omit for the series start |
| to | optional inclusive ISO UTC calendar day (YYYY-MM-DD); omit for today UTC (that day still in progress) |
| format | csv | markdown |
Query it
MCP tool call against https://dev.nostrolo.gy/mcp (connect your agent):
{
"name": "nostrology_query_metric",
"arguments": {
"metric": "catalog_size",
"domain": "routstr",
"grain": "day"
}
}Windowed (inclusive UTC days; both optional):
{
"name": "nostrology_query_metric",
"arguments": {
"metric": "catalog_size",
"domain": "routstr",
"grain": "day",
"from": "2026-07-01",
"to": "2026-07-31"
}
}Response: a plain-text envelope (window, freshness, column contract, this page's
caveats) followed by the data table (csv, or format: "markdown") at day grain.
Response columns
| name | type | description |
|---|---|---|
| utc_day | date | UTC day the catalog version was published |
| catalog_models | integer | number of models in that version of the curated list (each version is capped at 100 ids) |
| version_ordinal | integer | the version's position in the archive, oldest = 1 - the publication order within a day |
What is counted
Only the curated key's 'routstr-21-models' coordinate counts; an impostor pubkey and a ':usage:checkpoint:' experiment also publish on this kind and are ignored. Every version the archive holds is a row (relays keep only the latest).
Caveats
- For the models added and removed by each version use the routstr.catalog_versions reference record; for the current membership use routstr.model_catalog.
- Series is sparse and a day can repeat: two versions published on one UTC day are two rows, in publication order (version_ordinal).
Freshness in every response is data-derived: the newest routstr refresh's generation instant (nightly 02:45 UTC; the newest ledger day is the previous UTC day).