API REST core-node

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 endpoint · OpenAPI 3.1.0 · Specifica OpenAPI (JSON)

L'interfaccia completa della blockchain è il JSON-RPC. Questa è la piccola API REST che affianca il nodo e che l'API locale del miner usa per i metadati dei modelli e le metriche del nodo. In produzione è sulla porta 8050.

Endpoint

GET/

Root

Root endpoint - provides API information.

Risposte

StatoDescrizioneCorpo
200Successful Response
  • application/json any

GET/health

Health Check

Health check endpoint - no auth required.

Risposte

StatoDescrizioneCorpo
200Successful Response
  • application/json any

GET/api/v1/models

Get Models List

Get list of models with rate limiting.

Parametri

NomePosizioneTipoObbligatorioDescrizione
extendedqueryboolean—

Corpo della richiesta

Risposte

StatoDescrizioneCorpo
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.

Corpo della richiesta

Risposte

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

GET/api/v1/models/{model_hash}

Get Model Info

Get model information with input validation.

Parametri

NomePosizioneTipoObbligatorioDescrizione
model_hashpathstringSì

Corpo della richiesta

Risposte

StatoDescrizioneCorpo
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.

Corpo della richiesta

Risposte

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

Schemi

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"`

CampoTipoObbligatorioDescrizione
schemestringSì
credentialsstringSì

HTTPValidationError

CampoTipoObbligatorioDescrizione
detailValidationError[]—

ModelInfo

CampoTipoObbligatorioDescrizione
model_hashstringSì
model_namestringSì
model_commitstringSì
difficultyintegerSì
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

CampoTipoObbligatorioDescrizione
locstring | integer[]Sì
msgstringSì
typestringSì