Get capabilities

GET/v1/capabilities

TSCScan API v1.0.0 · Network · also at /api/v1/mainnet/capabilities

Chain-dependent response; compact chain headers identify the serving snapshot.

Example

curl 'https://api.tensorcash.org/v1/capabilities'

No parameters.

Status	Description	Body
`200`	Successful read from one Indexer snapshot	application/json `CapabilitiesResponse`
`400`	Invalid argument or page conditions	application/problem+json `Problem`
`401`	Authentication required	application/problem+json `Problem`
`403`	Permission denied	application/problem+json `Problem`
`404`	Absent in a ready indexed range	application/problem+json `Problem`
`409`	Verified chain continuity invalidation	application/problem+json `Problem`
`422`	Bounded response would exceed byte budget	application/problem+json `Problem`
`429`	Quota exceeded; Retry-After supplied	application/problem+json `Problem`
`503`	Data or eligible source not ready	application/problem+json `Problem`
`504`	Bounded upstream query timed out	application/problem+json `Problem`

Field	Type	Required	Description
`data`	`Capabilities`	Yes	The requested resource or collection; its schema is specific to this endpoint.

Field	Type	Required	Description
`blocks`	`boolean`	Yes	Number of blocks, or block-module availability/coverage, as specified by the enclosing schema.
`transactions`	`boolean`	Yes	Complete observed mempool count, confirmed transaction count or transaction-module availability/coverage, according to this schema.
`addresses`	`boolean`	Yes	Requested addresses or address-module availability, as specified by this schema.
`models`	`boolean`	Yes	Availability or indexed coverage of the Models module.
`assets`	`boolean`	Yes	Availability or indexed coverage of the Assets module.
`proof`	`boolean`	Yes	Compact Proof facts, or Proof-module availability/coverage, as specified by this schema.
`faucet`	`boolean`	Yes	Whether a Faucet API is enabled. It is currently false.
`market`	`boolean`	Yes	Whether Market data is enabled. Chain API resources never require Market data.

Field	Type	Required	Description
`type`	`string`	Yes	Problem type URI; about:blank is used for the current error family.
`title`	`string`	Yes	Short human-readable problem title, normally the stable error code.
`status`	`integer`	Yes	HTTP status code for this problem response.
`code`	`"INVALID_ARGUMENT" \| "UNAUTHORIZED" \| "FORBIDDEN" \| "RESOURCE_NOT_FOUND" \| "CHAIN_ANCHOR_INVALIDATED" \| "RATE_LIMITED" \| "DATA_NOT_READY" \| "SERVICE_UNAVAILABLE" \| "UPSTREAM_TIMEOUT" \| "RESPONSE_TOO_LARGE" \| "CORE_UNAVAILABLE" \| "CORE_METHOD_UNAVAILABLE" \| "CORE_DATA_NOT_READY" \| "CORE_CAPACITY" \| "TRANSACTION_CAPACITY" \| "TRANSACTION_STATE_CHANGED" \| "TRANSACTION_REJECTED" \| "BROADCAST_OUTCOME_UNKNOWN" \| "UNSUPPORTED_ASSET_POLICY"`	Yes	Stable machine-readable error code; use this instead of matching message text.
`request_id`	`string`	Yes	Identifier also supplied in X-Request-ID; include it when reporting an error.
`detail`	`string`	—	Human-readable explanation of the error.
`retry_after_seconds`	`integer`	—	Suggested wait in seconds before retrying; where present, agrees with Retry-After.