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 endpoints · OpenAPI 3.1.0 · Spécification OpenAPI (JSON)

L’interface complète de la chaîne, c’est le JSON-RPC. Ceci est la petite interface REST à côté du nœud, utilisée par l’API locale du mineur pour les métadonnées des modèles et les métriques du nœud. Port 8050 en production.

Endpoints

GET/

Root

Root endpoint - provides API information.

Réponses

StatutDescriptionCorps
200Successful Response
  • application/json any

GET/health

Health Check

Health check endpoint - no auth required.

Réponses

StatutDescriptionCorps
200Successful Response
  • application/json any

GET/api/v1/models

Get Models List

Get list of models with rate limiting.

Paramètres

NomEmplacementTypeRequisDescription
extendedqueryboolean—

Corps de la requête

Réponses

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

Corps de la requête

Réponses

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

GET/api/v1/models/{model_hash}

Get Model Info

Get model information with input validation.

Paramètres

NomEmplacementTypeRequisDescription
model_hashpathstringOui

Corps de la requête

Réponses

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

Corps de la requête

Réponses

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

Schémas

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

ChampTypeRequisDescription
schemestringOui
credentialsstringOui

ModelInfo

ChampTypeRequisDescription
model_hashstringOui
model_namestringOui
model_commitstringOui
difficultyintegerOui
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

ChampTypeRequisDescription
locstring | integer[]Oui
msgstringOui
typestringOui