REST-API van de 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 · OpenAPI-specificatie (JSON)

De volledige interface van de blockchain is de JSON-RPC. Dit is de kleine REST-interface naast de node, die door de lokale miner-API wordt gebruikt voor modelmetadata en nodestatistieken. In productie op poort 8050.

Endpoints

GET/

Root

Root endpoint - provides API information.

Responses

StatusBeschrijvingBody
200Successful Response
  • application/json any

GET/health

Health Check

Health check endpoint - no auth required.

Responses

StatusBeschrijvingBody
200Successful Response
  • application/json any

GET/api/v1/models

Get Models List

Get list of models with rate limiting.

Parameters

NaamLocatieTypeVerplichtBeschrijving
extendedqueryboolean—

Request-body

Responses

StatusBeschrijvingBody
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

Responses

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

GET/api/v1/models/{model_hash}

Get Model Info

Get model information with input validation.

Parameters

NaamLocatieTypeVerplichtBeschrijving
model_hashpathstringJa

Request-body

Responses

StatusBeschrijvingBody
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

Responses

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

Schema's

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

VeldTypeVerplichtBeschrijving
schemestringJa
credentialsstringJa

ModelInfo

VeldTypeVerplichtBeschrijving
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

VeldTypeVerplichtBeschrijving
locstring | integer[]Ja
msgstringJa
typestringJa