Network & analytics API
Read public subnet activity and analytical views with their source and freshness metadata.
GET /api/network
Returns observedAt and five independent sections: registry, sft, training, validator, and pay. Each section includes state and asOf. A failed source can be unavailable while other sections remain usable.
Network summary · public read
curl --fail-with-body --silent --show-error \
'https://api.reliqua.ai/api/network'| Section | Published information |
|---|---|
| registry | Task identity, mechanism, status, cap, job identity, and active cap total. |
| sft | Job states, prompt counts, acceptance, audit, proof, tokens, settlement, and countsComplete. |
| training | Run and model identities, candidate checkpoints, and published checkpoint revisions. |
| validator | Published checkpoint, repository, revision, and phase when available. |
| pay | Corpus pay estimate per active job: cap, maximum price, current-period projection, unsettled and recent settled periods. |
GET /api/pay
Returns the pay section alone, as published by the corpus validator: an estimate, not a promise. Per active period-settled job it gives the cap, the maximum price per verified token, the current period’s projection from the tokens verified so far, unsettled periods, and up to 12 settled periods with what each paid per million verified tokens.
Amounts are shares of the miners’ emission and, when the chain read is available, alpha per million tokens; no fiat conversion is made. Unknown values are null. What a hotkey receives also depends on consensus across validators and on settlement timing, described in note and settlementLagSeconds.
Corpus pay estimate · public read
curl --fail-with-body --silent --show-error \
'https://api.reliqua.ai/api/pay'GET /api/monitoring/analytics/:view
Returns the requested analytical snapshot with charts, tables, metrics, and source provenance. The workspace uses views such as network, generation, miners, chain, training, sft, evaluations, windows, ledger, and status.
Filters are validated. Common filters include lane, windows, and published entity identities. Use lane=all|math|code|logic and windows=12|24|48|96 for supported window views. Unsupported keys, repeated keys, or malformed identities return invalid_filters.
Network analytics · recent windows
curl --fail-with-body --silent --show-error \
'https://api.reliqua.ai/api/monitoring/analytics/network?lane=all&windows=24'History and collection health
GET /api/monitoring/history/:view is available for network, miners, chain, and status. It accepts range=24h|7d|30d, defaulting to 24h. Collected history depends on this deployment’s enabled sources and retained observations.
GET /api/monitoring/health describes public collection health. GET /api/monitoring/snapshot supplies the public widget snapshot used by custom dashboards. Saved board layouts are private session resources.
Retained network history
curl --fail-with-body --silent --show-error \
'https://api.reliqua.ai/api/monitoring/history/network?range=24h'Interpret responses carefully
- Use each source’s observation time; the response fetch time is a different clock.
- Retain null fields and unavailable states when storing snapshots.
- Check countsComplete before treating a count as complete.
- Keep measured observations separate from reference information.
- Use finalized-chain panels for finalized allocation evidence.
Network concepts — Understand the evidence behind each stage.
Monitoring guide — Explore the same sources in the workspace.