registry / v1

Operations

Registry gaps

Public read-only view of missing resources and enrichment priorities. Submit corrections through the GitHub repo.

github

Open gaps

127

5 high · 7 med · 115 low

updated 3h ago

High severity

needs attention

updated 3h ago

Avg completeness

80%

98 ≥75% · 5 <50%

129 scored

updated 3h ago

Adapter candidates

127

prioritized leads

updated 3h ago

Queue depth

129

awaiting enrichment

updated 3h ago

At a glance

Missing kinds across the registry

Click a row to filter the open-gaps section by that resource kind and jump straight to it.

Integrability scoreboard

Average score

80/ 100

Median score

78/ 100

Fully complete

2%3 subnets

Coverage by dimension

% of subnets

sse2
openapi47
community71
data-artifact92
website93
subnet-api94
source-repo96
docs100

Lowest-coverage dimensions first — the biggest gaps to fill.

Completeness scores

subnets

0-240
25-495
50-7426
75-9996
1002

How subnet completeness scores are distributed across the registry.

Coverage

What's actually missing

Subnets × required public-interface kinds. Cells link straight to that subnet's surfaces tab.

Coverage matrix

What each subnet is missing

Subnet	docs	repo	openapi	endpoint	dashboard	data	sdk	example	rpc	Comp
SN31Recall	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	25%
SN73MetaHash	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	40%
SN86Subnet 86	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	33%
SN27NI Compute	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	43%
SN30Endure Network	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	55%
SN81Grail	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	78%
SN90DegenBrain	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	78%
SN94Bitsota	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	73%
SN109Academia	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	63%
SN115HashiChain	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	63%
SN119Satori	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	48%
SN0root	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	90%
SN1Apex	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	93%
SN2DSperse	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	93%
SN3Templar	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	93%
SN4Targon	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	70%
SN5Hone	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	78%
SN6Numinous	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	93%
SN7Allways	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	100%
SN8Vanta	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	78%
SN9iota	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	93%
SN10Swap	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	86%
SN11TrajectoryRL	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	78%
SN12Compute Horde	docs Present	repo Present	openapi Present	endpoint Present	dashboard Present	data Present	sdk Present	example Present	rpc Present	70%

Distribution

Registry shape

Histogram of completeness across every scored profile. Median and quartile markers show where the registry sits today.

Distribution

Completeness across the registry

p2578%p5078%p7590%μ80%

129 subnets bucketed in 10% bins. Median (p50) marks the middle of the registry; long tail to the right is the goal.

Open gaps

Missing evidence, by priority

Filter by status, curation target, and missing resource kind.

StatusTargetSort127 of 127

highcandidate-discoveredSN27· NI Compute
NI Compute — 4 missing surfaces
Missing: website, openapi, subnet-api, sse
open file
highmaintainer-reviewedSN31· Recall
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.
open file
highmaintainer-reviewedSN73· MetaHash
MetaHash — 5 missing surfaces
Missing: source-repo, website, openapi, sse, data-artifact
↳ Native chain name currently reports as Parked; multiple public directories identify SN73 as MetaHash.
open file
highmaintainer-reviewedSN86· Subnet 86
Subnet 86 — 5 missing surfaces
Missing: source-repo, website, openapi, subnet-api, sse
↳ Native chain name is placeholder-like.
open file
highmaintainer-reviewedSN119· Satori
Satori — 4 missing surfaces
Missing: website, openapi, subnet-api, sse
↳ Previously discovered Satori119/Satori source repository currently returns 404.
open file
mediummaintainer-reviewedSN0· root
root — 4 missing surfaces
Missing: openapi, subnet-api, sse, data-artifact
↳ Root/system is not expected to expose subnet-specific SSE or data artifacts.
open file
mediummaintainer-reviewedSN30· Endure Network
Endure Network — 4 missing surfaces
Missing: source-repo, openapi, sse, data-artifact
↳ Official website and documentation are live and verified.
open file
mediumcommunity-seededSN38· ChronoLLM
ChronoLLM — 3 missing surfaces
Missing: openapi, subnet-api, sse
open file
mediummaintainer-reviewedSN104· for sale (burn to uid1)
for sale (burn to uid1) — 3 missing surfaces
Missing: openapi, subnet-api, sse
↳ Current chain identity is sale/placeholder-style rather than a clear product identity.
open file
mediummaintainer-reviewedSN109· Academia
Academia — 3 missing surfaces
Missing: website, openapi, sse
↳ No verified standalone website yet.
open file
mediummaintainer-reviewedSN115· HashiChain
HashiChain — 3 missing surfaces
Missing: website, openapi, sse
↳ No verified standalone website yet.
open file
mediummaintainer-reviewedSN122· Bitrecs
Bitrecs — 3 missing surfaces
Missing: openapi, subnet-api, sse
↳ No verified machine-readable OpenAPI/Swagger schema yet.
open file
lowmaintainer-reviewedSN1· Apex
Apex — 1 missing surface
Missing: sse
↳ The specific Apex docs URL resolves through the Macrocosmos docs site, but no machine-readable schema is available.
open file
lowmaintainer-reviewedSN2· DSperse
DSperse — 1 missing surface
Missing: sse
↳ Official website, docs, and source repository are verified live.
open file
lowmaintainer-reviewedSN3· Templar
Templar — 1 missing surface
Missing: sse
↳ Native chain name currently reports as deprecated.
open file
lowmaintainer-reviewedSN4· Targon
Targon — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ Official website, docs, Intel whitepaper, and source repository are verified live.
open file
lowmaintainer-reviewedSN5· Hone
Hone — 2 missing surfaces
Missing: openapi, sse
↳ Official website, network pages, and source repository are verified live.
open file
lowmaintainer-reviewedSN6· Numinous
Numinous — 1 missing surface
Missing: sse
↳ Official website, source repository, Swagger UI, OpenAPI schema, and health endpoint are verified live.
open file
lowmaintainer-reviewedSN8· Vanta
Vanta — 2 missing surfaces
Missing: openapi, sse
↳ Official website, dashboard, transparency page, tokenomics page, and source repository are verified live.
open file
lowmaintainer-reviewedSN9· iota
iota — 1 missing surface
Missing: sse
↳ Previously discovered IOTA docs URL currently returns 404.
open file
lowmaintainer-reviewedSN10· Swap
Swap — 1 missing surface
Missing: sse
↳ Official TaoFi pool page, docs, and Swap source repository are verified live.
open file
lowmaintainer-reviewedSN11· TrajectoryRL
TrajectoryRL — 2 missing surfaces
Missing: openapi, sse
↳ Official website, docs, leaderboard, live, winners, benchmark pages, and source repository are verified live.
open file
lowmaintainer-reviewedSN12· Compute Horde
Compute Horde — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ Project-linked Grafana metagraph dashboard is verified live.
open file
lowmaintainer-reviewedSN13· Data Universe
Data Universe — 1 missing surface
Missing: sse
↳ No verified machine-readable OpenAPI/Swagger schema yet.
open file
lowmaintainer-reviewedSN14· Cacheon
Cacheon — 1 missing surface
Missing: sse
↳ Official website, docs, source repository, and miner API contract documentation are verified live.
open file
lowmaintainer-reviewedSN15· ORO
ORO — 1 missing surface
Missing: sse
↳ No verified safe public subnet API endpoint yet.
open file
lowmaintainer-reviewedSN16· BitAds
BitAds — 1 missing surface
Missing: sse
↳ Official website, docs page, and source repository are verified live.
open file
lowcandidate-discoveredSN17· 404—GEN
404—GEN — 2 missing surfaces
Missing: openapi, sse
open file
lowcandidate-discoveredSN18· Zeus
Zeus — 1 missing surface
Missing: sse
open file
lowmaintainer-reviewedSN19· blockmachine
blockmachine — 1 missing surface
Missing: sse
↳ No verified safe public subnet API endpoint yet.
open file
lowmaintainer-reviewedSN20· GroundLayer
GroundLayer — 2 missing surfaces
Missing: openapi, sse
↳ Official website, subnet, and roadmap pages are live and verified.
open file
lowmaintainer-reviewedSN21· AdTAO
AdTAO — 1 missing surface
Missing: sse
↳ No verified official docs URL yet.
open file
lowmaintainer-reviewedSN22· Desearch
Desearch — 1 missing surface
Missing: sse
↳ No verified SSE/event stream yet.
open file
lowmaintainer-reviewedSN23· Trishool
Trishool — 2 missing surfaces
Missing: openapi, sse
↳ Trishool API root is public, but `/openapi.json` and `/docs` currently return 401 and `/swagger.json` returns 404.
open file
lowmaintainer-reviewedSN24· Quasar
Quasar — 2 missing surfaces
Missing: openapi, sse
↳ No verified OpenAPI/Swagger surface yet.
open file
lowmaintainer-reviewedSN25· Mainframe
Mainframe — 2 missing surfaces
Missing: openapi, sse
↳ Previously discovered Mainframe docs URL currently returns 404.
open file
lowcandidate-discoveredSN26· Perturb
Perturb — 2 missing surfaces
Missing: openapi, sse
open file
lowmaintainer-reviewedSN28· gm
gm — 1 missing surface
Missing: sse
↳ No verified official website yet.
open file
lowmaintainer-reviewedSN29· Coldint
Coldint — 2 missing surfaces
Missing: openapi, sse
↳ No verified machine-readable OpenAPI/Swagger schema yet.
open file
lowmaintainer-reviewedSN32· ItsAI
ItsAI — 2 missing surfaces
Missing: openapi, sse
↳ No verified official docs URL yet.
open file
lowmaintainer-reviewedSN33· ReadyAI
ReadyAI — 1 missing surface
Missing: sse
↳ No verified machine-readable OpenAPI/Swagger schema yet.
open file
lowmaintainer-reviewedSN34· BitMind
BitMind — 1 missing surface
Missing: sse
↳ No verified machine-readable OpenAPI/Swagger schema yet.
open file
lowcandidate-discoveredSN35· OxMarkets
OxMarkets — 1 missing surface
Missing: sse
open file
lowcandidate-discoveredSN36· Eirel
Eirel — 1 missing surface
Missing: sse
open file
lowcandidate-discoveredSN37· Aurelius
Aurelius — 1 missing surface
Missing: sse
open file
lowmaintainer-reviewedSN39· Basilica
Basilica — 2 missing surfaces
Missing: openapi, sse
↳ Native chain name currently reports as deprecated.
open file
lowmaintainer-reviewedSN40· Chunking
Chunking — 2 missing surfaces
Missing: openapi, sse
↳ subnet.chunking.com appears to be the official Chunking website, but its TLS certificate is currently expired and probe-derived status should be degraded.
open file
lowcommunity-seededSN41· Almanac
Almanac — 2 missing surfaces
Missing: openapi, sse
open file
lowmaintainer-reviewedSN42· Gopher
Gopher — 2 missing surfaces
Missing: openapi, sse
↳ Native chain name currently reports as a placeholder.
open file
lowmaintainer-reviewedSN43· Graphite
Graphite — 1 missing surface
Missing: sse
↳ No verified official docs URL yet.
open file
lowcandidate-discoveredSN44· Score
Score — 1 missing surface
Missing: sse
open file
lowmaintainer-reviewedSN45· Talisman AI
Talisman AI — 1 missing surface
Missing: sse
↳ No verified official docs URL yet.
open file
lowcommunity-seededSN46· Zipcode
Zipcode — 1 missing surface
Missing: sse
open file
lowmaintainer-reviewedSN47· EvolAI
EvolAI — 1 missing surface
Missing: sse
↳ No verified official website yet.
open file
lowmaintainer-reviewedSN48· Quantum Compute
Quantum Compute — 2 missing surfaces
Missing: openapi, sse
↳ No verified official docs URL yet.
open file
lowmaintainer-reviewedSN49· Nepher Robotics
Nepher Robotics — 1 missing surface
Missing: sse
↳ No verified SSE/event stream yet.
open file
lowcommunity-seededSN50· Synth
Synth — 1 missing surface
Missing: sse
open file
lowcommunity-seededSN51· lium.io
lium.io — 1 missing surface
Missing: sse
open file
lowmaintainer-reviewedSN52· Dojo
Dojo — 1 missing surface
Missing: sse
↳ No verified machine-readable OpenAPI/Swagger schema yet.
open file
lowmaintainer-reviewedSN53· EfficientFrontier
EfficientFrontier — 1 missing surface
Missing: sse
↳ SignalPlus website is live and is tracked as the team/project website.
open file
lowcommunity-seededSN54· Yanez MIID
Yanez MIID — 1 missing surface
Missing: sse
open file
lowcommunity-seededSN55· NIOME
NIOME — 2 missing surfaces
Missing: openapi, sse
open file
lowmaintainer-reviewedSN56· Gradients
Gradients — 1 missing surface
Missing: sse
↳ Machine-readable OpenAPI schema is verified at https://api.gradients.io/openapi.json.
open file
lowmaintainer-reviewedSN57· Sparket
Sparket — 2 missing surfaces
Missing: openapi, sse
↳ No verified official docs URL yet.
open file
lowmaintainer-reviewedSN58· Handshake58
Handshake58 — 1 missing surface
Missing: sse
↳ No verified SSE/event stream yet.
open file
lowcommunity-seededSN59· Babelbit
Babelbit — 1 missing surface
Missing: sse
open file
lowcommunity-seededSN60· Bitsec
Bitsec — 1 missing surface
Missing: sse
open file
lowmaintainer-reviewedSN61· RedTeam
RedTeam — 1 missing surface
Missing: sse
↳ No verified safe public subnet API endpoint yet.
open file
lowmaintainer-reviewedSN62· Ridges
Ridges — 2 missing surfaces
Missing: sse, data-artifact
↳ Website exists but currently rate-limits simple probes.
open file
lowmaintainer-reviewedSN63· Enigma
Enigma — 2 missing surfaces
Missing: openapi, sse
↳ No verified official docs URL yet.
open file
lowcommunity-seededSN65· TAO Private Network
TAO Private Network — 1 missing surface
Missing: sse
open file
lowmaintainer-reviewedSN66· ninja
ninja — 2 missing surfaces
Missing: openapi, sse
↳ Swagger/OpenAPI routes currently serve HTML UI only; no verified machine-readable schema URL yet.
open file
lowcommunity-seededSN67· Harnyx
Harnyx — 2 missing surfaces
Missing: openapi, sse
open file
lowcommunity-seededSN68· NOVA
NOVA — 1 missing surface
Missing: sse
open file
lowmaintainer-reviewedSN69· ain
ain — 2 missing surfaces
Missing: openapi, sse
↳ No publicly verified team/operator profile yet.
open file
lowcommunity-seededSN70· NexisGen
NexisGen — 1 missing surface
Missing: sse
open file
lowcommunity-seededSN71· Leadpoet
Leadpoet — 1 missing surface
Missing: sse
open file
lowmaintainer-reviewedSN72· StreetVision by NATIX
StreetVision by NATIX — 2 missing surfaces
Missing: openapi, sse
↳ No verified machine-readable OpenAPI/Swagger schema yet.
open file
lowadapter-backedSN74· Gittensor
Gittensor — 1 missing surface
Missing: sse
↳ No verified dashboard surface yet.
open file
lowmaintainer-reviewedSN75· Hippius
Hippius — 1 missing surface
Missing: sse
↳ No verified machine-readable OpenAPI/Swagger schema yet.
open file
lowmaintainer-reviewedSN76· Byzantium
Byzantium — 2 missing surfaces
Missing: openapi, sse
↳ No verified docs site yet.
open file
lowcommunity-seededSN77· Liquidity
Liquidity — 2 missing surfaces
Missing: openapi, sse
open file
lowcommunity-seededSN78· Vocence
Vocence — 1 missing surface
Missing: sse
open file
lowmaintainer-reviewedSN79· MVTRX
MVTRX — 2 missing surfaces
Missing: openapi, sse
↳ Public paper link redirects to Proton Drive and is not a documentation site.
open file
lowcommunity-seededSN80· dogelayer
dogelayer — 2 missing surfaces
Missing: openapi, sse
open file
lowmaintainer-reviewedSN81· Grail
Grail — 2 missing surfaces
Missing: website, sse
↳ Native chain name currently reports as deprecated.
open file
lowmaintainer-reviewedSN82· Compelle
Compelle — 2 missing surfaces
Missing: openapi, sse
↳ No verified official docs URL yet.
open file
lowcommunity-seededSN83· CliqueAI
CliqueAI — 2 missing surfaces
Missing: openapi, sse
open file
lowmaintainer-reviewedSN84· ansuz
ansuz — 2 missing surfaces
Missing: openapi, sse
↳ No verified machine-readable OpenAPI/Swagger schema yet.
open file
lowmaintainer-reviewedSN85· Vidaio
Vidaio — 1 missing surface
Missing: sse
↳ Website docs and dashboard paths currently redirect to sign-in.
open file
lowmaintainer-reviewedSN87· Luminar Network
Luminar Network — 2 missing surfaces
Missing: openapi, sse
↳ No verified source repository yet.
open file
lowmaintainer-reviewedSN88· Investing
Investing — 2 missing surfaces
Missing: openapi, sse
↳ Public asset-list surface is HTML/table content, not a schema-backed API.
open file
lowmaintainer-reviewedSN89· InfiniteHash
InfiniteHash — 2 missing surfaces
Missing: openapi, sse
↳ Project homepage currently returns HTTP 402.
open file
lowmaintainer-reviewedSN90· DegenBrain
DegenBrain — 2 missing surfaces
Missing: source-repo, sse
↳ Native chain name currently reports as ogham while the project website identifies SN90 as DegenBrain/Brain.
open file
lowmaintainer-reviewedSN91· Bitstarter #1
Bitstarter #1 — 2 missing surfaces
Missing: openapi, sse
↳ Official website, app, how-it-works, and project submission pages are live and verified.
open file
lowmaintainer-reviewedSN92· Tensorclaw
Tensorclaw — 2 missing surfaces
Missing: openapi, sse
↳ Native chain name currently reports as luis while the public website identifies the project as Tensorclaw Network / Subnet 92.
open file
lowcandidate-discoveredSN93· Bitcast
Bitcast — 1 missing surface
Missing: sse
open file
lowcommunity-seededSN94· Bitsota
Bitsota — 2 missing surfaces
Missing: website, sse
open file
lowmaintainer-reviewedSN95· Actual
Actual — 2 missing surfaces
Missing: openapi, sse
↳ Previously discovered GitHub organization/source candidate currently returns 404.
open file
lowmaintainer-reviewedSN96· Verathos
Verathos — 1 missing surface
Missing: sse
↳ No verified SSE/event stream yet.
open file
lowcommunity-seededSN97· Albedo
Albedo — 1 missing surface
Missing: sse
open file
lowmaintainer-reviewedSN98· ForeverMoney
ForeverMoney — 1 missing surface
Missing: sse
↳ No verified official docs URL yet.
open file
lowcommunity-seededSN99· Leoma
Leoma — 1 missing surface
Missing: sse
open file
lowmaintainer-reviewedSN100· Plaτform
Plaτform — 1 missing surface
Missing: sse
↳ Official website, docs, and source repository are verified.
open file
lowmaintainer-reviewedSN101· eni
eni — 3 missing surfaces
Missing: openapi, sse, data-artifact
↳ No verified official website yet.
open file
lowmaintainer-reviewedSN102· ConnitoAI
ConnitoAI — 1 missing surface
Missing: sse
↳ Previously discovered Connito miner docs URL currently returns 404.
open file
lowmaintainer-reviewedSN103· Djinn
Djinn — 2 missing surfaces
Missing: openapi, sse
↳ No verified official docs URL yet.
open file
lowcommunity-seededSN105· Beam
Beam — 1 missing surface
Missing: sse
open file
lowmaintainer-reviewedSN106· Nodexo
Nodexo — 2 missing surfaces
Missing: openapi, sse
↳ 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.
open file
lowcommunity-seededSN107· Minos
Minos — 3 missing surfaces
Missing: openapi, sse, data-artifact
open file
lowcommunity-seededSN108· TalkHead
TalkHead — 2 missing surfaces
Missing: openapi, sse
open file
lowmaintainer-reviewedSN110· Green Compute
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.
open file
lowmaintainer-reviewedSN111· oneoneone
oneoneone — 2 missing surfaces
Missing: openapi, sse
↳ No verified official docs URL yet.
open file
lowcommunity-seededSN112· minotaur
minotaur — 2 missing surfaces
Missing: openapi, sse
open file
lowmaintainer-reviewedSN113· TensorUSD
TensorUSD — 2 missing surfaces
Missing: openapi, sse
↳ No verified safe public subnet API endpoint yet.
open file
lowmaintainer-reviewedSN114· SOMA
SOMA — 2 missing surfaces
Missing: openapi, sse
↳ Official website, dashboard, MCP/access pages, and DendriteHQ source repository are verified.
open file
lowmaintainer-reviewedSN116· TaoLend
TaoLend — 2 missing surfaces
Missing: openapi, sse
↳ Native chain name currently reports as hard_sign; public directories identify SN116 as TaoLend.
open file
lowmaintainer-reviewedSN117· BrainPlay
BrainPlay — 2 missing surfaces
Missing: openapi, sse
↳ Native chain name is a placeholder.
open file
lowmaintainer-reviewedSN118· Ditto
Ditto — 2 missing surfaces
Missing: openapi, sse
↳ Official website, docs, assistant app, and GitHub organization repository listing are verified.
open file
lowcommunity-seededSN120· Affine
Affine — 1 missing surface
Missing: sse
open file
lowmaintainer-reviewedSN121· sundae_bar
sundae_bar — 2 missing surfaces
Missing: openapi, sse
↳ No verified official docs URL yet.
open file
lowmaintainer-reviewedSN123· MANTIS
MANTIS — 2 missing surfaces
Missing: openapi, sse
↳ No verified standalone website yet.
open file
lowcommunity-seededSN124· Swarm
Swarm — 2 missing surfaces
Missing: openapi, sse
open file
lowmaintainer-reviewedSN125· 8 Ball
8 Ball — 2 missing surfaces
Missing: openapi, sse
↳ Official website and miner/source repository are verified live.
open file
lowcommunity-seededSN126· Poker44
Poker44 — 2 missing surfaces
Missing: openapi, sse
open file
lowcommunity-seededSN127· Astrid
Astrid — 2 missing surfaces
Missing: openapi, sse
open file
lowcommunity-seededSN128· ByteLeap
ByteLeap — 3 missing surfaces
Missing: openapi, sse, data-artifact
open file

Coverage

Profile completeness

Per-subnet completeness across required public-interface kinds.

SN31
25%
SN86
33%
SN73
40%
SN27
43%
SN119
48%
SN30
55%
SN104
63%
SN38
58%
SN107
65%
SN101
70%
SN122
63%
SN4
70%
SN128
65%
SN109
63%
SN115
63%
SN82
78%
SN17
73%
SN108
73%
SN48
78%
SN63
78%
SN32
78%
SN79
78%
SN121
78%
SN55
73%

Pilots

Adapter candidates

Subnets where a maintained adapter would unlock the highest registry value.

SN64snapshot schema shape and consider normalized metrics from stable read-only operations538
SN7maintain and deepen existing adapter metrics345
SN74maintain and deepen existing adapter metrics268
SN15snapshot schema shape and consider normalized metrics from stable read-only operations242
SN49snapshot schema shape and consider normalized metrics from stable read-only operations219
SN56snapshot schema shape and consider normalized metrics from stable read-only operations219
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
SN110snapshot schema shape and consider normalized metrics from stable read-only operations154
SN94snapshot schema shape and consider normalized metrics from stable read-only operations153
SN93snapshot schema shape and consider normalized metrics from stable read-only operations139
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
SN51snapshot schema shape and consider normalized metrics from stable read-only operations135
SN24evaluate data-artifact freshness and schema normalization134
SN33snapshot schema shape and consider normalized metrics from stable read-only operations134
SN37snapshot schema shape and consider normalized metrics from stable read-only operations134
SN68snapshot schema shape and consider normalized metrics from stable read-only operations134
SN43snapshot schema shape and consider normalized metrics from stable read-only operations133
SN90snapshot schema shape and consider normalized metrics from stable read-only operations133
SN72evaluate data-artifact freshness and schema normalization116
SN34snapshot schema shape and consider normalized metrics from stable read-only operations115
SN6snapshot schema shape and consider normalized metrics from stable read-only operations112
SN53snapshot schema shape and consider normalized metrics from stable read-only operations95
SN75snapshot schema shape and consider normalized metrics from stable read-only operations95
SN45snapshot schema shape and consider normalized metrics from stable read-only operations94
SN52snapshot schema shape and consider normalized metrics from stable read-only operations94
SN97snapshot schema shape and consider normalized metrics from stable read-only operations93
SN18snapshot schema shape and consider normalized metrics from stable read-only operations92
SN46snapshot schema shape and consider normalized metrics from stable read-only operations92
SN70snapshot schema shape and consider normalized metrics from stable read-only operations92
SN111evaluate data-artifact freshness and schema normalization92
SN28snapshot schema shape and consider normalized metrics from stable read-only operations91
SN59snapshot schema shape and consider normalized metrics from stable read-only operations91
SN85snapshot schema shape and consider normalized metrics from stable read-only operations91
SN13snapshot schema shape and consider normalized metrics from stable read-only operations80
SN1snapshot schema shape and consider normalized metrics from stable read-only operations76
SN66evaluate data-artifact freshness and schema normalization75
SN35snapshot schema shape and consider normalized metrics from stable read-only operations74
SN100snapshot schema shape and consider normalized metrics from stable read-only operations74
SN2snapshot schema shape and consider normalized metrics from stable read-only operations73
SN3snapshot schema shape and consider normalized metrics from stable read-only operations73
SN16snapshot schema shape and consider normalized metrics from stable read-only operations73
SN65snapshot schema shape and consider normalized metrics from stable read-only operations73
SN106evaluate data-artifact freshness and schema normalization73
SN9snapshot schema shape and consider normalized metrics from stable read-only operations72
SN38evaluate data-artifact freshness and schema normalization72
SN42evaluate data-artifact freshness and schema normalization72
SN60snapshot schema shape and consider normalized metrics from stable read-only operations72
SN81snapshot schema shape and consider normalized metrics from stable read-only operations72
SN87evaluate data-artifact freshness and schema normalization72
SN98snapshot schema shape and consider normalized metrics from stable read-only operations72
SN103evaluate data-artifact freshness and schema normalization72
SN105snapshot schema shape and consider normalized metrics from stable read-only operations72
SN107review public-safe API evidence before adding a custom adapter72
SN113evaluate data-artifact freshness and schema normalization72
SN10snapshot schema shape and consider normalized metrics from stable read-only operations71
SN44snapshot schema shape and consider normalized metrics from stable read-only operations71
SN47snapshot schema shape and consider normalized metrics from stable read-only operations71
SN50snapshot schema shape and consider normalized metrics from stable read-only operations71
SN61snapshot schema shape and consider normalized metrics from stable read-only operations71
SN71snapshot schema shape and consider normalized metrics from stable read-only operations71
SN78snapshot schema shape and consider normalized metrics from stable read-only operations71
SN88evaluate data-artifact freshness and schema normalization71
SN123evaluate data-artifact freshness and schema normalization71
SN124evaluate data-artifact freshness and schema normalization71
SN21snapshot schema shape and consider normalized metrics from stable read-only operations70
SN54snapshot schema shape and consider normalized metrics from stable read-only operations70
SN95evaluate data-artifact freshness and schema normalization70
SN102snapshot schema shape and consider normalized metrics from stable read-only operations70
SN120snapshot schema shape and consider normalized metrics from stable read-only operations70
SN99snapshot schema shape and consider normalized metrics from stable read-only operations68
SN118evaluate data-artifact freshness and schema normalization57
SN4review public-safe API evidence before adding a custom adapter54
SN11evaluate data-artifact freshness and schema normalization54
SN29evaluate data-artifact freshness and schema normalization54
SN91evaluate data-artifact freshness and schema normalization54
SN5evaluate data-artifact freshness and schema normalization52
SN8evaluate data-artifact freshness and schema normalization52
SN23evaluate data-artifact freshness and schema normalization52
SN32evaluate data-artifact freshness and schema normalization52
SN80evaluate data-artifact freshness and schema normalization52
SN89evaluate data-artifact freshness and schema normalization52
SN114evaluate data-artifact freshness and schema normalization52
SN20evaluate data-artifact freshness and schema normalization51
SN25evaluate data-artifact freshness and schema normalization51
SN39evaluate data-artifact freshness and schema normalization51
SN40evaluate data-artifact freshness and schema normalization51
SN83evaluate data-artifact freshness and schema normalization51
SN112evaluate data-artifact freshness and schema normalization51
SN117evaluate data-artifact freshness and schema normalization51
SN122evaluate data-artifact freshness and schema normalization51
SN17evaluate data-artifact freshness and schema normalization50
SN26evaluate data-artifact freshness and schema normalization50
SN41evaluate data-artifact freshness and schema normalization50
SN48evaluate data-artifact freshness and schema normalization50
SN76evaluate data-artifact freshness and schema normalization50
SN77evaluate data-artifact freshness and schema normalization50
SN79evaluate data-artifact freshness and schema normalization50
SN84evaluate data-artifact freshness and schema normalization50
SN92evaluate data-artifact freshness and schema normalization50
SN125evaluate data-artifact freshness and schema normalization50
SN127evaluate data-artifact freshness and schema normalization50
SN55evaluate data-artifact freshness and schema normalization49
SN57evaluate data-artifact freshness and schema normalization49
SN62snapshot schema shape and consider normalized metrics from stable read-only operations49
SN63evaluate data-artifact freshness and schema normalization49
SN67evaluate data-artifact freshness and schema normalization49
SN69evaluate data-artifact freshness and schema normalization49
SN82evaluate data-artifact freshness and schema normalization49
SN108evaluate data-artifact freshness and schema normalization49
SN116evaluate data-artifact freshness and schema normalization49
SN121evaluate data-artifact freshness and schema normalization49
SN126evaluate data-artifact freshness and schema normalization49
SN109evaluate data-artifact freshness and schema normalization48
SN115evaluate data-artifact freshness and schema normalization48
SN12review public-safe API evidence before adding a custom adapter30
SN128review public-safe API evidence before adding a custom adapter29
SN27evaluate data-artifact freshness and schema normalization28
SN30review public-safe API evidence before adding a custom adapter28
SN101review public-safe API evidence before adding a custom adapter28
SN104evaluate data-artifact freshness and schema normalization28
SN73review public-safe API evidence before adding a custom adapter26
SN86evaluate data-artifact freshness and schema normalization26
SN119evaluate data-artifact freshness and schema normalization26

Queue

Enrichment queue

Prioritized list of registry entries awaiting verification or enrichment.

ID	Netuid	Priority	Note
sn-64	SN64	380	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	182	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
gradients	SN56	174	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.
sn-49	SN49	160	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-94	SN94	158	Submit one official public website candidate with npm run surface:add.
sn-51	SN51	140	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-93	SN93	138	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-38	SN38	137	Submit one official public openapi, subnet-api candidate with npm run surface:add.
sn-37	SN37	136	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-68	SN68	136	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-107	SN107	132	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-24	SN24	130	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-22	SN22	128	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-27	SN27	126	Submit one official public website candidate with npm run surface:add.
sn-110	SN110	125	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-72	SN72	124	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
cacheon	SN14	123	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-86	SN86	122	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-70	SN70	118	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-90	SN90	117	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-46	SN46	111	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
metahash	SN73	110	Submit one official public website, source-repo candidate with npm run surface:add.
sn-124	SN124	110	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-58	SN58	105	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-17	SN17	105	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-18	SN18	105	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-59	SN59	104	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-108	SN108	104	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-112	SN112	102	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-26	SN26	101	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-55	SN55	101	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-126	SN126	101	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-127	SN127	101	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-67	SN67	100	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-80	SN80	100	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-81	SN81	99	Submit one official public website candidate with npm run surface:add.
sn-97	SN97	99	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
satori	SN119	97	Submit one official public website candidate with npm run surface:add.
sn-4	SN4	96	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-103	SN103	96	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
nodexo	SN106	96	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-122	SN122	96	Submit one official public openapi, subnet-api candidate with npm run surface:add.
sn-41	SN41	96	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-77	SN77	95	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-83	SN83	95	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-30	SN30	94	Submit one official public source-repo candidate with npm run surface:add.
sn-128	SN128	94	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
numinous	SN6	93	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-33	SN33	93	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-117	SN117	93	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
actual	SN95	92	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
for-sale-uid1	SN104	92	Submit one official public openapi, subnet-api candidate with npm run surface:add.
sn-54	SN54	92	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-43	SN43	91	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-88	SN88	90	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-65	SN65	90	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-111	SN111	89	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-66	SN66	88	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-113	SN113	88	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-35	SN35	88	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-75	SN75	86	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-82	SN82	86	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-109	SN109	86	Submit one official public website candidate with npm run surface:add.
sn-44	SN44	86	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-78	SN78	86	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-120	SN120	86	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-32	SN32	85	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-48	SN48	85	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-118	SN118	85	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-115	SN115	85	Submit one official public website candidate with npm run surface:add.
sn-60	SN60	85	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-63	SN63	84	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-79	SN79	84	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-39	SN39	84	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-50	SN50	84	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-105	SN105	84	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-89	SN89	83	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-121	SN121	83	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-123	SN123	83	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-71	SN71	83	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
eni	SN101	82	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-25	SN25	81	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-85	SN85	81	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
efficientfrontier	SN53	80	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-5	SN5	76	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-114	SN114	76	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-99	SN99	76	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
chunking	SN40	75	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.
sn-87	SN87	75	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-11	SN11	74	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
gm	SN28	74	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-8	SN8	73	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-20	SN20	73	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-23	SN23	73	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-3	SN3	73	Maintainer should review current machine-verified surfaces and promote only source-backed entries.
sn-13	SN13	72	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-21	SN21	72	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-76	SN76	72	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-29	SN29	71	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-45	SN45	71	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-91	SN91	71	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-100	SN100	71	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-1	SN1	70	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-9	SN9	70	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
ain	SN69	69	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-98	SN98	68	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-52	SN52	65	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-10	SN10	64	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-12	SN12	62	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
dsperse	SN2	61	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-84	SN84	61	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-47	SN47	60	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-92	SN92	60	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
taolend	SN116	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-57	SN57	59	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-16	SN16	58	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-61	SN61	58	Maintainer should evaluate whether subnet-specific adapter metrics add useful public operational data.
sn-102	SN102	58	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.
root	SN0	11	No immediate enrichment action; keep monitoring for drift and new public interfaces.