core-node REST-API

Small REST surface exposed by the TensorCash core-node alongside the JSON-RPC server. Used by the miner-api to query model metadata and node metrics. The full chain surface is the JSON-RPC at /docs/rpc/.

6 Endpunkte · OpenAPI 3.1.0 · OpenAPI-Spezifikation (JSON)

Die vollständige Schnittstelle zur Chain ist die JSON-RPC-Schnittstelle. Dies ist die kleine REST-Schnittstelle neben dem Node, die die lokale Miner-API für Modell-Metadaten und Node-Metriken nutzt. In Produktion auf Port 8050.

Endpunkte

GET/

Root

Root endpoint - provides API information.

Antworten

StatusBeschreibungBody
200Successful Response
  • application/json any

GET/health

Health Check

Health check endpoint - no auth required.

Antworten

StatusBeschreibungBody
200Successful Response
  • application/json any

GET/api/v1/models

Get Models List

Get list of models with rate limiting.

Parameter

NameOrtTypPflichtBeschreibung
extendedqueryboolean—

Request-Body

Antworten

StatusBeschreibungBody
200Successful Response
422Validation Error

GET/api/v1/blockchaininfo

Get Blockchain Info

Pass-through to the node's getblockchaininfo RPC. Used by the verification orchestrator to compute distance-to-verdict for PendingVerification model records and trigger anticipatory smell-stat pre-bake before a model flips to Registered.

Request-Body

Antworten

StatusBeschreibungBody
200Successful Response
  • application/json any
422Validation Error

GET/api/v1/models/{model_hash}

Get Model Info

Get model information with input validation.

Parameter

NameOrtTypPflichtBeschreibung
model_hashpathstringJa

Request-Body

Antworten

StatusBeschreibungBody
200Successful Response
  • application/json any
422Validation Error

GET/api/v1/miner/metrics

Get Miner Metrics

Get mining throughput metrics from the miner proxy. Returns token throughput (tokens/sec), completion rate, and totals.

Request-Body

Antworten

StatusBeschreibungBody
200Successful Response
  • application/json any
422Validation Error

Schemas

HTTPAuthorizationCredentials

The HTTP authorization credentials in the result of using HTTPBearer or HTTPDigest in a dependency. The HTTP authorization header value is split by the first space. The first part is the scheme, the second part is the credentials. For example, in an HTTP Bearer token scheme, the client will send a header like: `` Authorization: Bearer deadbeef12346 ` In this case: * scheme will have the value "Bearer" * credentials will have the value "deadbeef12346"`

FeldTypPflichtBeschreibung
schemestringJa
credentialsstringJa

ModelInfo

FeldTypPflichtBeschreibung
model_hashstringJa
model_namestringJa
model_commitstringJa
difficultyintegerJa
statusinteger | null—
cidstring | null—
extrastring | null—
txidstring | null—
block_hashstring | null—
block_heightinteger | null—
deposit_txidstring | null—
deposit_voutinteger | null—
deposit_amountinteger | null—
owner_key_hashstring | null—
deposit_block_hashstring | null—
deposit_block_heightinteger | null—
commit_txidstring | null—
commit_block_hashstring | null—
commit_block_heightinteger | null—
verification_codeinteger | null—
verification_detailsstring | null—

ValidationError

FeldTypPflichtBeschreibung
locstring | integer[]Ja
msgstringJa
typestringJa