Agents subnets
Agents on Bittensor today
13 subnets are classified under agents. 11 publish at least one first-party interface and 13 have a surface that answered our most recent probe. Agent subnets tend to publish fewer synchronous endpoints and more artifacts, so the useful signal is often the source repository and the evaluation method rather than an uptime figure. Read what the validator scores; it tells you more about what the subnet produces than any description does.
| Subnet | Readiness | Surfaces | Health |
|---|---|---|---|
| SN6 Numinous | 100 | 6/27 | |
| SN62 Ridges | 100 | 9/50 | |
| SN98 NeverPlayAlone | 100 | 2/12 | |
| SN118 Ditto | 100 | 21/31 | |
| SN1 Apex | 96 | 3/47 | |
| SN15 ORO | 96 | 3/91 | |
| SN74 Gittensor | 96 | 0/58 | |
| SN11 TrajectoryRL | 86 | 7/15 | |
| SN87 Provenonce | 86 | 4/14 | |
| SN92 Enclave | 86 | 0/13 | |
| SN121 sundae_bar | 83 | 5/19 | |
| SN66 conjectures | 81 | 6/13 | |
| SN115 HashiChain | 74 | 1/8 |
What "agents" means here
Subnets where the unit of work is a task completed rather than a response returned — code written, a trajectory planned, a workflow executed — usually with a longer feedback loop than an inference call.
How the classification is derived
Categories come from what a subnet publishes about itself — its declared purpose, its source repository and the interfaces it exposes — not from a hand-maintained list. A subnet can belong to several, and 60 of 129 currently belong to none, which is a coverage gap in our data rather than a statement about those subnets.