Skip to main content
Metagraphed
Netuid 027· application

Nodexo

· ג

Reviewed overlay for SN27 Nodexo Compute. 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.

ReviewedUnknown
WebsiteDocsRepositoryDashboard
Participants
256
Tempo
360
Endpoints
9
Completeness
55%
Integration readiness
13/ 100Dormant
Unknown
Start here: Nodexo website · nodexo
Callable APICallable nowDocumentedAuth clarityProfile completeActive
0 operational interfaces · missing openapi, subnet-api, sse, data-artifact

Economics

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

Loading economics…

Endpoints at a glance

Root RPC/WSS, SSE/data streams, and open incidents — one tap to expand.

  • Root RPC / WSS0
    —
  • SSE / Data0
    —
  • Incidents (open)0
    —

Surfaces

Curated public interfaces, grouped by kind.

dashboard4
source-repo1
+ 1 more group — open the Surfaces tab.

Schema drift

OpenAPI/JSON Schema snapshots joined from /api/v1/schemas.

No tracked schemas

OpenAPI/JSON Schema URLs verified for this subnet will show here once captured.

Last checked
Browse all schemas

Reliability

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

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

Growth

Completeness, surfaces, and endpoints across recent weekly snapshots.

Loading growth…

Uptime history

Daily uptime per surface and an overall reliability grade, over 90d/1y.

—
Loading uptime…

Known gaps

Missing resources, profile incompleteness, and curation notes.

Missing kinds
openapisubnet-apissedata-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.