Skip to main content
RegistrySubnets / 006

Numinous

ζapplicationbaseline-augmentedbaseline-curatedforecastingidentity-reviewed

Reviewed overlay for SN6 Numinous. The public API exposes Swagger UI, a machine-readable OpenAPI 3.1 schema, and a read-only health endpoint.

Netuid
006
Native chain id
updated 1h ago
Participants
256
Active UIDs
updated 1h ago · weekly window
Endpoints
12
tracked
updated 1h ago
Surfaces
12
7 kinds supported
updated 1h ago
Uptime
current window
updated 1h ago · 90d window
Latency p50
median probe latency
updated 1h ago · 90d window
Completeness
93%
maintainer-reviewed
registry profile
updated 1h ago
Evidence
4
primary sources
updated 1h ago
Integration readiness
86/ 100Ready to integrate
Unknown
Start here: Numinous API health · numinous
Callable APICallable nowDocumentedAuth clarityProfile completeActive
3 operational interfaces · missing sse

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
Completeness93%
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
sse
  • · Official website, source repository, Swagger UI, OpenAPI schema, and health endpoint are verified live.
  • · 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.