Skip to main content
Metagraphed
Netuid 023· application

Trishool

· ψ

Reviewed overlay for SN23 using the official Trishool dashboard, phase-two source repository, and public API landing URL. The API root returns a public landing response, but OpenAPI and docs paths currently require auth or return 404, so no schema-backed API is promoted.

ReviewedUnknown
WebsiteDocsRepositoryDashboard
Participants
256
Tempo
360
Endpoints
11
Completeness
70%
Integration readiness
83/ 100Ready to integrate
Unknown
Start here: Trishool API landing · trishool
Callable APICallable nowDocumentedAuth clarityProfile completeActive
1 operational interface · missing openapi, 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.

dashboard3
source-repo2
+ 2 more groups — 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
openapissedata-artifact
  • · Trishool API root is public, but `/openapi.json` and `/docs` currently return 401 and `/swagger.json` returns 404.
  • · No verified machine-readable OpenAPI/Swagger schema 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.