Registry gaps
Public read-only view of missing resources and enrichment priorities. Submit corrections through the GitHub repo.
Integrability scoreboard
Coverage by dimension
% of subnets- sse2
- openapi31
- data-artifact33
- subnet-api45
- community68
- website91
- source-repo95
- docs100
Lowest-coverage dimensions first — the biggest gaps to fill.
Completeness scores
subnets- 0-240
- 25-4912
- 50-7481
- 75-9933
- 1003
How subnet completeness scores are distributed across the registry.
What each subnet is missing
Completeness across the registry
129 subnets bucketed in 10% bins. Median (p50) marks the middle of the registry; long tail to the right is the goal.
- NI Compute — 5 missing surfaces
Missing: website, openapi, subnet-api, sse, data-artifact
- Endure Network — 5 missing surfaces
Missing: source-repo, openapi, subnet-api, sse, data-artifact
↳ Official website and documentation are live and verified.
- Recall — 6 missing surfaces
Missing: source-repo, website, openapi, subnet-api, sse, data-artifact
↳ Public chain/directory sources show a recent Halftime to Recall identity change.
- ChronoLLM — 4 missing surfaces
Missing: website, openapi, subnet-api, sse
- ain — 5 missing surfaces
Missing: source-repo, openapi, subnet-api, sse, data-artifact
↳ No publicly verified team/operator profile yet.
- MetaHash — 6 missing surfaces
Missing: source-repo, website, openapi, subnet-api, sse, data-artifact
↳ Native chain name currently reports as Parked; multiple public directories identify SN73 as MetaHash.
- Subnet 86 — 6 missing surfaces
Missing: source-repo, website, openapi, subnet-api, sse, data-artifact
↳ Native chain name is placeholder-like.
- for sale (burn to uid1) — 6 missing surfaces
Missing: source-repo, website, openapi, subnet-api, sse, data-artifact
↳ Current chain identity is sale/placeholder-style rather than a clear product identity.
- Academia — 4 missing surfaces
Missing: website, openapi, subnet-api, sse
↳ No verified standalone website yet.
- HashiChain — 5 missing surfaces
Missing: website, openapi, subnet-api, sse, data-artifact
↳ No verified standalone website yet.
- Satori — 5 missing surfaces
Missing: website, openapi, subnet-api, sse, data-artifact
↳ Previously discovered Satori119/Satori source repository currently returns 404.
- MANTIS — 4 missing surfaces
Missing: website, openapi, subnet-api, sse
↳ No verified standalone website yet.
- root — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ Root/system is not expected to expose subnet-specific SSE or data artifacts.
- Apex — 3 missing surfaces
Missing: openapi, subnet-api, sse
↳ The specific Apex docs URL resolves through the Macrocosmos docs site, but no machine-readable schema is available.
- DSperse — 3 missing surfaces
Missing: openapi, subnet-api, sse
↳ Official website, docs, and source repository are verified live.
- Hone — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ Official website, network pages, and source repository are verified live.
- Vanta — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ Official website, dashboard, transparency page, tokenomics page, and source repository are verified live.
- iota — 3 missing surfaces
Missing: openapi, subnet-api, sse
↳ Previously discovered IOTA docs URL currently returns 404.
- Swap — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ Official TaoFi pool page, docs, and Swap source repository are verified live.
- Compute Horde — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ Project-linked Grafana metagraph dashboard is verified live.
- BitAds — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ Official website, docs page, and source repository are verified live.
- 404—GEN — 3 missing surfaces
Missing: openapi, subnet-api, sse
- GroundLayer — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ Official website, subnet, and roadmap pages are live and verified.
- Quasar — 3 missing surfaces
Missing: openapi, subnet-api, sse
↳ No verified OpenAPI/Swagger surface yet.
- Mainframe — 3 missing surfaces
Missing: openapi, subnet-api, sse
↳ Previously discovered Mainframe docs URL currently returns 404.
- Coldint — 3 missing surfaces
Missing: openapi, subnet-api, sse
↳ No verified machine-readable OpenAPI/Swagger schema yet.
- OxMarkets — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
- Chunking — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ subnet.chunking.com appears to be the official Chunking website, but its TLS certificate is currently expired and probe-derived status should be degraded.
- Almanac — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ No verified OpenAPI/Swagger surface yet.
- Score — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
- Quantum Compute — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ No verified official docs URL yet.
- Dojo — 3 missing surfaces
Missing: openapi, subnet-api, sse
↳ No verified machine-readable OpenAPI/Swagger schema yet.
- EfficientFrontier — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ SignalPlus website is live and is tracked as the team/project website.
- Yanez MIID — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
- NIOME — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ No verified OpenAPI/Swagger surface yet.
- TAO Private Network — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
- Harnyx — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
- StreetVision by NATIX — 3 missing surfaces
Missing: openapi, subnet-api, sse
↳ No verified machine-readable OpenAPI/Swagger schema yet.
- Byzantium — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ No verified docs site yet.
- Liquidity — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ No verified OpenAPI/Swagger surface yet.
- MVTRX — 3 missing surfaces
Missing: openapi, subnet-api, sse
↳ Public paper link redirects to Proton Drive and is not a documentation site.
- dogelayer — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
- Grail — 4 missing surfaces
Missing: website, openapi, sse, data-artifact
↳ Native chain name currently reports as deprecated.
- CliqueAI — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ No verified OpenAPI/Swagger surface yet.
- ansuz — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ No verified machine-readable OpenAPI/Swagger schema yet.
- Investing — 3 missing surfaces
Missing: openapi, subnet-api, sse
↳ Public asset-list surface is HTML/table content, not a schema-backed API.
- InfiniteHash — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ Project homepage currently returns HTTP 402.
- Bitstarter #1 — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ Official website, app, how-it-works, and project submission pages are live and verified.
- Tensorclaw — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ Native chain name currently reports as luis while the public website identifies the project as Tensorclaw Network / Subnet 92.
- ForeverMoney — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ No verified official docs URL yet.
- Plaτform — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ Official website, docs, and source repository are verified.
- eni — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ No verified official website yet.
- ConnitoAI — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ Previously discovered Connito miner docs URL currently returns 404.
- Beam — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
- oneoneone — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ No verified official docs URL yet.
- minotaur — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
- TaoLend — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ Native chain name currently reports as hard_sign; public directories identify SN116 as TaoLend.
- Ditto — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ Official website, docs, assistant app, and GitHub organization repository listing are verified.
- sundae_bar — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ No verified official docs URL yet.
- Bitrecs — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ No verified machine-readable OpenAPI/Swagger schema yet.
- Swarm — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
- Poker44 — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ No verified OpenAPI/Swagger surface yet.
- Astrid — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ No verified OpenAPI/Swagger surface yet.
- ByteLeap — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ No verified OpenAPI/Swagger surface yet.
- Templar — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ Native chain name currently reports as deprecated.
- Targon — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ Official website, docs, Intel whitepaper, and source repository are verified live.
- Numinous — 1 missing surface
Missing: sse
↳ Official website, source repository, Swagger UI, OpenAPI schema, and health endpoint are verified live.
- TrajectoryRL — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ Official website, docs, leaderboard, live, winners, benchmark pages, and source repository are verified live.
- Data Universe — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ No verified machine-readable OpenAPI/Swagger schema yet.
- Cacheon — 1 missing surface
Missing: sse
↳ Official website, docs, source repository, and miner API contract documentation are verified live.
- ORO — 1 missing surface
Missing: sse
↳ No verified safe public subnet API endpoint yet.
- blockmachine — 1 missing surface
Missing: sse
↳ No verified safe public subnet API endpoint yet.
- AdTAO — 2 missing surfaces
Missing: sse, data-artifact
↳ No verified official docs URL yet.
- Desearch — 1 missing surface
Missing: sse
↳ No verified SSE/event stream yet.
- Trishool — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ Trishool API root is public, but `/openapi.json` and `/docs` currently return 401 and `/swagger.json` returns 404.
- Perturb — 3 missing surfaces
Missing: openapi, sse, data-artifact
- gm — 2 missing surfaces
Missing: sse, data-artifact
↳ No verified official website yet.
- ItsAI — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ No verified official docs URL yet.
- ReadyAI — 1 missing surface
Missing: sse
↳ No verified machine-readable OpenAPI/Swagger schema yet.
- BitMind — 1 missing surface
Missing: sse
↳ No verified machine-readable OpenAPI/Swagger schema yet.
- Basilica — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ Native chain name currently reports as deprecated.
- Gopher — 2 missing surfaces
Missing: openapi, sse
↳ Native chain name currently reports as a placeholder.
- Graphite — 1 missing surface
Missing: sse
↳ No verified official docs URL yet.
- Talisman AI — 3 missing surfaces
Missing: subnet-api, sse, data-artifact
↳ No verified official docs URL yet.
- EvolAI — 1 missing surface
Missing: sse
↳ No verified official website yet.
- Nepher Robotics — 1 missing surface
Missing: sse
↳ No verified SSE/event stream yet.
- Synth — 3 missing surfaces
Missing: subnet-api, sse, data-artifact
↳ No verified subnet API surface yet.
- Gradients — 1 missing surface
Missing: sse
↳ Machine-readable OpenAPI schema is verified at https://api.gradients.io/openapi.json.
- Sparket — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ No verified official docs URL yet.
- Handshake58 — 1 missing surface
Missing: sse
↳ No verified SSE/event stream yet.
- Bitsec.ai — 3 missing surfaces
Missing: subnet-api, sse, data-artifact
↳ No verified subnet API surface yet.
- RedTeam — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ No verified safe public subnet API endpoint yet.
- Ridges — 2 missing surfaces
Missing: sse, data-artifact
↳ Website exists but currently rate-limits simple probes.
- Enigma — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ No verified official docs URL yet.
- ninja — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ Swagger/OpenAPI routes currently serve HTML UI only; no verified machine-readable schema URL yet.
- Leadpoet — 3 missing surfaces
Missing: subnet-api, sse, data-artifact
- Gittensor — 1 missing surface
Missing: sse
↳ No verified dashboard surface yet.
- Hippius — 1 missing surface
Missing: sse
↳ No verified machine-readable OpenAPI/Swagger schema yet.
- Compelle — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ No verified official docs URL yet.
- Vidaio — 1 missing surface
Missing: sse
↳ Website docs and dashboard paths currently redirect to sign-in.
- Luminar Network — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ No verified source repository yet.
- DegenBrain — 3 missing surfaces
Missing: source-repo, sse, data-artifact
↳ Native chain name currently reports as ogham while the project website identifies SN90 as DegenBrain/Brain.
- Actual — 2 missing surfaces
Missing: openapi, sse
↳ Previously discovered GitHub organization/source candidate currently returns 404.
- Verathos — 1 missing surface
Missing: sse
↳ No verified SSE/event stream yet.
- Leoma — 3 missing surfaces
Missing: subnet-api, sse, data-artifact
↳ No verified subnet API surface yet.
- Djinn — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ No verified official docs URL yet.
- Nodexo — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ Official website/docs/console are browser-facing but currently reject simple machine probes with connection resets, so these surfaces are listed without recurring probe monitoring.
- Green Compute — 1 missing surface
Missing: sse
↳ No verified source repository has been promoted as official because the discovered repository identifies a different Rich Kids of TAO subnet identity.
- TensorUSD — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ No verified safe public subnet API endpoint yet.
- SOMA — 2 missing surfaces
Missing: openapi, sse
↳ Official website, dashboard, MCP/access pages, and DendriteHQ source repository are verified.
- BrainPlay — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ Native chain name is a placeholder.
- Affine — 3 missing surfaces
Missing: subnet-api, sse, data-artifact
↳ No verified subnet API surface yet.
- 8 Ball — 2 missing surfaces
Missing: openapi, sse
↳ Official website and miner/source repository are verified live.
- SN64snapshot schema shape and consider normalized metrics from stable read-only operations454
- SN7maintain and deepen existing adapter metrics345
- SN74maintain and deepen existing adapter metrics268
- SN15snapshot schema shape and consider normalized metrics from stable read-only operations221
- SN56snapshot schema shape and consider normalized metrics from stable read-only operations198
- SN36snapshot schema shape and consider normalized metrics from stable read-only operations178
- SN22snapshot schema shape and consider normalized metrics from stable read-only operations160
- SN14snapshot schema shape and consider normalized metrics from stable read-only operations158
- SN49snapshot schema shape and consider normalized metrics from stable read-only operations156
- SN110snapshot schema shape and consider normalized metrics from stable read-only operations154
- SN58snapshot schema shape and consider normalized metrics from stable read-only operations137
- SN96snapshot schema shape and consider normalized metrics from stable read-only operations136
- SN19snapshot schema shape and consider normalized metrics from stable read-only operations135
- SN43snapshot schema shape and consider normalized metrics from stable read-only operations133
- SN94snapshot schema shape and consider normalized metrics from stable read-only operations132
- SN34snapshot schema shape and consider normalized metrics from stable read-only operations115
- SN24evaluate data-artifact freshness and schema normalization113
- SN33snapshot schema shape and consider normalized metrics from stable read-only operations113
- SN6snapshot schema shape and consider normalized metrics from stable read-only operations112
- SN90snapshot schema shape and consider normalized metrics from stable read-only operations112
- SN75snapshot schema shape and consider normalized metrics from stable read-only operations95
- SN51snapshot schema shape and consider normalized metrics from stable read-only operations93
- SN97snapshot schema shape and consider normalized metrics from stable read-only operations93
- SN46snapshot schema shape and consider normalized metrics from stable read-only operations92
- SN68evaluate data-artifact freshness and schema normalization92
- SN93snapshot schema shape and consider normalized metrics from stable read-only operations76
- SN42evaluate data-artifact freshness and schema normalization72
- SN18snapshot schema shape and consider normalized metrics from stable read-only operations71
- SN37snapshot schema shape and consider normalized metrics from stable read-only operations71
- SN47snapshot schema shape and consider normalized metrics from stable read-only operations71
- SN28snapshot schema shape and consider normalized metrics from stable read-only operations70
- SN59snapshot schema shape and consider normalized metrics from stable read-only operations70
- SN85snapshot schema shape and consider normalized metrics from stable read-only operations70
- SN95evaluate data-artifact freshness and schema normalization70
- SN66review public-safe API evidence before adding a custom adapter53
- SN72evaluate data-artifact freshness and schema normalization53
- SN45snapshot schema shape and consider normalized metrics from stable read-only operations52
- SN52evaluate data-artifact freshness and schema normalization52
- SN106review public-safe API evidence before adding a custom adapter52
- SN114evaluate data-artifact freshness and schema normalization52
- SN107review public-safe API evidence before adding a custom adapter51
- SN50snapshot schema shape and consider normalized metrics from stable read-only operations50
- SN70snapshot schema shape and consider normalized metrics from stable read-only operations50
- SN78snapshot schema shape and consider normalized metrics from stable read-only operations50
- SN125evaluate data-artifact freshness and schema normalization50
- SN21snapshot schema shape and consider normalized metrics from stable read-only operations49
- SN38evaluate data-artifact freshness and schema normalization49
- SN62snapshot schema shape and consider normalized metrics from stable read-only operations49
- SN88evaluate data-artifact freshness and schema normalization49
- SN13review public-safe API evidence before adding a custom adapter38
- SN1evaluate data-artifact freshness and schema normalization34
- SN4review public-safe API evidence before adding a custom adapter33
- SN11review public-safe API evidence before adding a custom adapter33
- SN29evaluate data-artifact freshness and schema normalization33
- SN2evaluate data-artifact freshness and schema normalization31
- SN3review public-safe API evidence before adding a custom adapter31
- SN23review public-safe API evidence before adding a custom adapter31
- SN32review public-safe API evidence before adding a custom adapter31
- SN9evaluate data-artifact freshness and schema normalization30
- SN25evaluate data-artifact freshness and schema normalization30
- SN39review public-safe API evidence before adding a custom adapter30
- SN60snapshot schema shape and consider normalized metrics from stable read-only operations30
- SN81review public-safe API evidence before adding a custom adapter30
- SN87review public-safe API evidence before adding a custom adapter30
- SN99snapshot schema shape and consider normalized metrics from stable read-only operations30
- SN103review public-safe API evidence before adding a custom adapter30
- SN113review public-safe API evidence before adding a custom adapter30
- SN17evaluate data-artifact freshness and schema normalization29
- SN26review public-safe API evidence before adding a custom adapter29
- SN61review public-safe API evidence before adding a custom adapter29
- SN71snapshot schema shape and consider normalized metrics from stable read-only operations29
- SN79evaluate data-artifact freshness and schema normalization29
- SN117review public-safe API evidence before adding a custom adapter29
- SN57review public-safe API evidence before adding a custom adapter28
- SN63review public-safe API evidence before adding a custom adapter28
- SN82review public-safe API evidence before adding a custom adapter28
- SN108review public-safe API evidence before adding a custom adapter28
- SN120snapshot schema shape and consider normalized metrics from stable read-only operations28
- SN123evaluate data-artifact freshness and schema normalization28
- SN109evaluate data-artifact freshness and schema normalization27
- SN118review public-safe API evidence before adding a custom adapter15
- SN35review public-safe API evidence before adding a custom adapter11
- SN100review public-safe API evidence before adding a custom adapter11
- SN122review public-safe API evidence before adding a custom adapter11
- SN5review public-safe API evidence before adding a custom adapter10
- SN8review public-safe API evidence before adding a custom adapter10
- SN65review public-safe API evidence before adding a custom adapter10
- SN89review public-safe API evidence before adding a custom adapter10
- SN91review public-safe API evidence before adding a custom adapter10
- SN12review public-safe API evidence before adding a custom adapter9
- SN20review public-safe API evidence before adding a custom adapter9
- SN40review public-safe API evidence before adding a custom adapter9
- SN80review public-safe API evidence before adding a custom adapter9
- SN105review public-safe API evidence before adding a custom adapter9
- SN10review public-safe API evidence before adding a custom adapter8
- SN41review public-safe API evidence before adding a custom adapter8
- SN44review public-safe API evidence before adding a custom adapter8
- SN76review public-safe API evidence before adding a custom adapter8
- SN77review public-safe API evidence before adding a custom adapter8
- SN83review public-safe API evidence before adding a custom adapter8
- SN98review public-safe API evidence before adding a custom adapter8
- SN102review public-safe API evidence before adding a custom adapter8
- SN112review public-safe API evidence before adding a custom adapter8
- SN124review public-safe API evidence before adding a custom adapter8
- SN128review public-safe API evidence before adding a custom adapter8
- SN30review public-safe API evidence before adding a custom adapter7
- SN48review public-safe API evidence before adding a custom adapter7
- SN54review public-safe API evidence before adding a custom adapter7
- SN55review public-safe API evidence before adding a custom adapter7
- SN67review public-safe API evidence before adding a custom adapter7
- SN101review public-safe API evidence before adding a custom adapter7
- SN121review public-safe API evidence before adding a custom adapter7
- SN126review public-safe API evidence before adding a custom adapter7
- SN127review public-safe API evidence before adding a custom adapter7
- SN69review public-safe API evidence before adding a custom adapter6
| ID | Netuid | Priority | Note |
|---|---|---|---|
| sn-64 | SN64 | 322 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| allways | SN7 | 232 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| gittensor | SN74 | 185 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-15 | SN15 | 167 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-36 | SN36 | 161 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| gradients | SN56 | 160 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-68 | SN68 | 159 | Submit one official public openapi, subnet-api candidate with npm run surface:add. |
| sn-94 | SN94 | 144 | Submit one official public website candidate with npm run surface:add. |
| sn-24 | SN24 | 141 | Submit one official public openapi, subnet-api candidate with npm run surface:add. |
| sn-38 | SN38 | 140 | Submit one official public website candidate with npm run surface:add. |
| sn-22 | SN22 | 128 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-110 | SN110 | 125 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-51 | SN51 | 124 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| cacheon | SN14 | 123 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-27 | SN27 | 121 | Submit one official public website candidate with npm run surface:add. |
| metahash | SN73 | 119 | Submit one official public website, source-repo candidate with npm run surface:add. |
| recall | SN31 | 118 | Submit one official public website, source-repo candidate with npm run surface:add. |
| sn-86 | SN86 | 118 | Submit one official public website, source-repo candidate with npm run surface:add. |
| for-sale-uid1 | SN104 | 118 | Submit one official public website, source-repo candidate with npm run surface:add. |
| sn-49 | SN49 | 117 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-107 | SN107 | 117 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-17 | SN17 | 116 | Submit one official public openapi, subnet-api candidate with npm run surface:add. |
| sn-90 | SN90 | 116 | Submit one official public source-repo candidate with npm run surface:add. |
| sn-19 | SN19 | 114 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-54 | SN54 | 113 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-65 | SN65 | 112 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-112 | SN112 | 112 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-55 | SN55 | 111 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-80 | SN80 | 111 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-126 | SN126 | 111 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-46 | SN46 | 111 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-67 | SN67 | 110 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-127 | SN127 | 110 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-35 | SN35 | 109 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-81 | SN81 | 109 | Submit one official public website candidate with npm run surface:add. |
| sn-50 | SN50 | 109 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-44 | SN44 | 108 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-93 | SN93 | 108 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-41 | SN41 | 106 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-72 | SN72 | 106 | Submit one official public openapi, subnet-api candidate with npm run surface:add. |
| sn-124 | SN124 | 106 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-128 | SN128 | 106 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-58 | SN58 | 105 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-30 | SN30 | 105 | Submit one official public source-repo candidate with npm run surface:add. |
| ain | SN69 | 105 | Submit one official public source-repo candidate with npm run surface:add. |
| sn-77 | SN77 | 105 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-83 | SN83 | 105 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-105 | SN105 | 105 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-37 | SN37 | 105 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-18 | SN18 | 103 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-59 | SN59 | 103 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-108 | SN108 | 103 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-96 | SN96 | 102 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-88 | SN88 | 101 | Submit one official public openapi, subnet-api candidate with npm run surface:add. |
| sn-70 | SN70 | 101 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-26 | SN26 | 99 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-97 | SN97 | 99 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-109 | SN109 | 97 | Submit one official public website candidate with npm run surface:add. |
| sn-123 | SN123 | 97 | Submit one official public website candidate with npm run surface:add. |
| sn-99 | SN99 | 97 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-120 | SN120 | 96 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| nodexo | SN106 | 95 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-79 | SN79 | 95 | Submit one official public openapi, subnet-api candidate with npm run surface:add. |
| sn-118 | SN118 | 95 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-60 | SN60 | 95 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-48 | SN48 | 94 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| numinous | SN6 | 93 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-1 | SN1 | 93 | Submit one official public openapi, subnet-api candidate with npm run surface:add. |
| sn-9 | SN9 | 93 | Submit one official public openapi, subnet-api candidate with npm run surface:add. |
| sn-25 | SN25 | 93 | Submit one official public openapi, subnet-api candidate with npm run surface:add. |
| sn-89 | SN89 | 93 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| eni | SN101 | 93 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| satori | SN119 | 93 | Submit one official public website candidate with npm run surface:add. |
| sn-121 | SN121 | 93 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-71 | SN71 | 93 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-100 | SN100 | 92 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-115 | SN115 | 92 | Submit one official public website candidate with npm run surface:add. |
| sn-43 | SN43 | 91 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| actual | SN95 | 90 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-52 | SN52 | 88 | Submit one official public openapi, subnet-api candidate with npm run surface:add. |
| sn-91 | SN91 | 87 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-66 | SN66 | 86 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-75 | SN75 | 86 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-5 | SN5 | 86 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-82 | SN82 | 85 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| chunking | SN40 | 85 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-78 | SN78 | 85 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| dsperse | SN2 | 84 | Submit one official public openapi, subnet-api candidate with npm run surface:add. |
| sn-32 | SN32 | 83 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-63 | SN63 | 83 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-8 | SN8 | 83 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-20 | SN20 | 83 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-3 | SN3 | 83 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-39 | SN39 | 83 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-13 | SN13 | 82 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-29 | SN29 | 82 | Submit one official public openapi, subnet-api candidate with npm run surface:add. |
| sn-76 | SN76 | 82 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-98 | SN98 | 82 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-4 | SN4 | 81 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-45 | SN45 | 81 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-122 | SN122 | 81 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-103 | SN103 | 80 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-117 | SN117 | 80 | Maintainer should review current machine-verified surfaces and promote only source-backed entries. |
| sn-10 | SN10 | 79 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-102 | SN102 | 79 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-33 | SN33 | 78 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-34 | SN34 | 78 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-114 | SN114 | 77 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-42 | SN42 | 75 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| gm | SN28 | 73 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-11 | SN11 | 72 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-113 | SN113 | 72 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-23 | SN23 | 71 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-12 | SN12 | 71 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-21 | SN21 | 70 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-61 | SN61 | 68 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-85 | SN85 | 67 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| efficientfrontier | SN53 | 67 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-84 | SN84 | 67 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| taolend | SN116 | 67 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-16 | SN16 | 66 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-92 | SN92 | 66 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-111 | SN111 | 66 | Submit one official public openapi, subnet-api, data-artifact candidate with npm run surface:add. |
| sn-87 | SN87 | 61 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-57 | SN57 | 60 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| eightball | SN125 | 60 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-62 | SN62 | 57 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| sn-47 | SN47 | 56 | Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data. |
| root | SN0 | 1 | No immediate enrichment action; keep monitoring for drift and new public interfaces. |