Skip to main content

Subnets with an API spec

Every subnet answers a probe; far fewer publish a contract you can generate a client from. These are the ones with a machine-readable API specification, scored on how completely they document it and checked against a live probe rather than a claim.

What the registry currently shows

66 of 129 catalogued subnets publish a machine-readable API specification. 57 of those score 90 or above on integration readiness, and 47 answered their most recent probe. Every figure here is computed from this registry's own 15-minute probe cycle, not from operator claims.

Bittensor subnets publishing a machine-readable API specification, ranked by integration readiness
SubnetReadinessServicesLast probe
SN2 DSperse10014/14Healthy
SN6 Numinous10020/20Healthy
SN7 Allways10041/41Healthy
SN12 Compute Horde1005/5Healthy
SN14 Cacheon10015/15
SN16 BitAds1003/3Healthy
SN19 blockmachine10027/27Healthy
SN22 Desearch10042/42Healthy
SN33 ReadyAI10014/14Healthy
SN35 OxMarkets10059/59Healthy
SN36 Leoma10029/29Healthy
SN44 Score10016/16Healthy
SN47 EvolAI1004/4
SN49 Nepher Robotics100141/141Healthy
SN51 lium.io100151/151Healthy
SN52 Dojo1004/4Healthy
SN53 engy1008/8Healthy
SN54 Yanez1006/6Healthy
SN56 Gradients10060/60Healthy
SN59 Babelbit10018/18Healthy
SN61 RedTeam1003/3Healthy
SN62 Ridges10042/43
SN65 TAO Private Network10015/15Healthy
SN71 Leadpoet1006/6Healthy
SN75 Hippius10039/39Healthy
SN85 Vidaio10012/12Healthy
SN90 KubeTEE10011/11Healthy
SN93 Bitcast100130/130Healthy
SN97 Albedo1004/4Healthy
SN98 NeverPlayAlone1004/4
SN99 Thirty Spokes1001/1Unknown
SN118 Ditto10016/16
SN120 Affine1005/11
SN3 Templar979/9Healthy
SN81 Grail973/3Unknown
SN1 Apex9634/34Healthy
SN13 Data Universe9613/13Healthy
SN15 ORO9680/80Healthy
SN18 Zeus968/8Healthy
SN38 ChronoLLM9613/13Healthy
SN64 Chutes9663/63
SN74 Gittensor9642/42Healthy
SN96 Verathos9658/58
SN105 Beam9630/30Healthy
SN110 Green Compute96103/103Healthy
SN113 TensorUSD966/6Healthy
SN9 iota9319/19Healthy
SN21 AdTAO9314/14Healthy
SN28 gm9313/13Healthy
SN45 AlphaRidge.ai9342/42
SN46 Instant9341/42
SN50 Synth9332/32Healthy
SN60 Bitsec.ai9331/32
SN68 NOVA9313/13Healthy
SN69 Herald9340/40Healthy
SN78 Vocence9348/48Healthy
SN34 BitMind9212/12Healthy
SN10 Pareton863/3Unknown
SN58 greevils861/6
SN102 ConnitoAI837/7Healthy
SN70 ghayn793/3
SN37 Aurelius7155/61
SN100 BASE7128/29Healthy
SN114 SOMA6849/49Healthy
SN43 Graphite6433/33
SN94 Bitsota5726/39

What counts as an API here

A subnet qualifies when it publishes a machine-readable specification — an OpenAPI document — not merely an endpoint that returns something. That distinction is the whole point: an address you can reach tells you nothing about what to send it, and a contract you can generate a client from is the difference between an integration and an afternoon of guessing.

Integration readiness

The readiness score is ours, derived from what a subnet actually publishes: whether the specification exists, whether examples accompany it, whether the endpoints it declares answer when probed, and whether the operator rather than a harvester is the source. It describes documentation quality, not the quality of the subnet's work.

How to read the probe column

Health is measured on a 15-minute cycle and recorded as observed — no operator sets it and neither do we. A subnet that publishes a perfect specification and fails its probe is telling you something real, and it is shown that way rather than quietly excluded.