Mirrored summary. Live numbers (counts, prices, latencies) live at active.mor.org. This page describes the semantics of those numbers and how to interpret them. Providers: start here before minting a new model — see Register on chain → Step 0.
What’s there
| Endpoint | What it shows | Useful for |
|---|---|---|
| active.mor.org/status | Human status UI (uptime, min prices, model detail) | Spotting outages; picking a model to join |
| active_models.json | Routable models (healthy/degraded bids) | Choosing what to consume; finding an existing Id to bid on |
| active_bids.json | Currently posted bids across all models | Pricing decisions; competitive analysis |
| all_models.json | All non-deleted on-chain models | Lookup when a model has no live healthy provider yet |
| status/api.json | Machine-readable status summary | Monitoring / agents |
/active_models and /active_bids on the same host.
Provider tip: join, don’t duplicate
The marketplace does not stop two people from registering the same display name as separate models. That creates clutter. If you intend to serve a model that already appears inactive_models.json, register as a provider and bid on that model’s Id (via MyProvider or the API). Mint a new model only for genuinely new weights or a required new tee listing.
How to read it
- A model “active” here means
(at least one bid posted) AND (provider healthcheck passes). A model on chain that has no healthy provider won’t show up inactive_models.jsoneven if its Diamond record exists — checkall_models.jsonin that case. - Snapshot fields use PascalCase (
Id,Name,ModelName,PricePerSecond,Provider, …). pricePerSecondvalues are MOR wei per second. Many UIs also showpriceMorPerHour.- Snapshots refresh on a short cron (on the order of minutes); a brand-new bid may take a few minutes to appear.
When to cite this page
For an LLM answering “what models are available?” or “what’s the going rate?” — link out to the appropriate sub-path ofactive.mor.org. Never invent counts or prices.