Skip to main content
RegistrySubnets / 106

Nodexo

Դapplicationbaseline-augmentedbaseline-curatedcomputegpu

Reviewed overlay for SN106 Nodexo Compute (on-chain SubnetIdentitiesV3 netuid 106 = subnet_name "Nodexo", subnet_url nodexo.ai; re-keyed from netuid 27, which on-chain is "Team TBC"). Official browser-facing website, docs, and console surfaces are known, but simple Node/HEAD probes currently receive connection resets. The previously discovered source repository candidate currently returns 404 and is not promoted.

Netuid
106
Native chain id
updated 1h ago
Participants
256
Active UIDs
updated 1h ago · weekly window
Endpoints
12
tracked
updated 1h ago
Surfaces
12
5 kinds supported
updated 1h ago
Uptime
current window
updated 1h ago · 90d window
Latency p50
median probe latency
updated 1h ago · 90d window
Completeness
70%
maintainer-reviewed
registry profile
updated 1h ago
Evidence
4
primary sources
updated 1h ago
Integration readiness
86/ 100Ready to integrate
Unknown
Start here: Nodexo app health · nodexo
Callable APICallable nowDocumentedAuth clarityProfile completeActive
1 operational interface · missing openapi, sse, data-artifact

Public resources

Endpoints, curated surfaces, and tracked schemas for this subnet.

Subnet profile

Chain identity, AMM economics, ownership keys, and registry curation.

Tempo
360
Type
application
Reg. block
Mechanisms
1
Ownership
No ownership keys recorded.
Registry curationReviewed
Completeness70%
probedmaintainer-reviewedconf · highreviewed

Economics

On-chain emission share, stake, validators, and market data.

Loading economics…

Network history

Daily on-chain neuron/validator counts, total stake, and emission over time.

Reliability

Per-surface uptime SLA and latency percentiles (p50/p95/p99) over 7d/30d.

Per-surface reliability · uptime · latency percentiles
Loading reliability…

Sources & evidence

Primary links and recorded evidence backing this profile.

Incident history

Recorded health regressions and SLA breaks for this subnet.

Known gaps

Missing resources, profile incompleteness, and curation notes.

Missing kinds
openapissedata-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.
  • · Common /docs, /api, /health, /openapi.json, and Swagger paths on nodexo.ai are not promoted because the origin rejects simple machine probes.
  • · Previously discovered GitHub source repository candidates currently return 404.
  • · No verified live source repository yet.
  • · No verified machine-readable OpenAPI/Swagger schema yet.
  • · No verified safe public subnet API endpoint yet.
  • · No verified SSE/event stream yet.
  • · No verified standalone static data artifact yet.
Help close these gaps by opening a PR against the public registry repo.