Skip to main content
Metagraphed
Netuid 116· application

TaoLend

· ъ

Reviewed overlay for SN116 TaoLend. Native chain identity currently reports hard_sign, while public subnet directories identify SN116 as TaoLend. The official website is tracked but currently returns server errors to simple probes. The previously discovered source repository currently returns 404 and is not promoted.

ReviewedUnknown
Participants
76
Tempo
360
Endpoints
7
Completeness
55%
Integration readiness
10/ 100Dormant
Unknown
Start here: TaoLend website · taolend
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.

dashboard3
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
  • · Native chain name currently reports as hard_sign; public directories identify SN116 as TaoLend.
  • · Official website currently returns 500/server-error responses to simple probes and should appear degraded until it recovers.
  • · Previously discovered GitHub source repository currently returns 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.