GET

Explorer · assets

List assets

/api/v2/explorer/assets

AUTHENTICATIONNone · publicService ownerasset-registry-read-modelContract sourceOpenAPISTATUSProduction listed

Purpose and usage

What this endpoint does

List assets from the public Explorer read model, with the identifiers and verification metadata defined by the live contract.

When to use it

Call this when an explorer, wallet, indexer, auditor, or research agent needs to discover assets and choose a canonical record for a later step so it can resolve public network state from a machine-readable projection.

OUTCOME · Discover

What changes

Read-only projection; it grants no mutation, settlement, traffic, or authority change.

WHY IT MATTERS

Gives people and agents a contract-backed way to discover assets.
Keeps website presentation separate from the stable public contract that wallets, indexers, and agents can ingest.

ISOLATION + AUTHORITY

This is a public, read-only Explorer projection. It exposes only fields admitted by the live OpenAPI schema; it grants no owner, wallet, signing, settlement, publisher, matching, or trading authority. Indexed observation time is not the same as chain finality.

BEFORE YOU CALL

No bearer credential is required; apply bounded filters and canonical public identifiers where the contract provides them.
Use the live OpenAPI schema as the authority for the exact request shape and response model.
Account for projection freshness, indexing position, and chain or domain finality in the consuming decision.

WHAT TO DO NEXT

Select one canonical identifier from the response and open its detail operation when the live contract exposes one.
Follow the returned canonical identifiers and proof or related-resource links when independent verification is required.

AGENT GUIDANCE

Use assets only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
Use the live OpenAPI schema as the authority for the exact request shape and response model.
Treat observation timestamps, indexing position, proof state, and finality as separate facts; do not infer final settlement or authority from presence in an Explorer result.
Use response links and canonical identifiers instead of constructing internal service URLs or scraping the website.

Contract reference

Use the deployed OpenAPI for exact parameters, schemas and security requirements. The tables below provide integration guidance.

Open this operation in OpenAPI

Request and response

Make the request

Examples illustrate integration intent; the referenced OpenAPI operation and component schemas define the executable shape.

PARAMETERS

Headers, path, query, and body

NAMELOCATIONPRESENCETYPE / RULES / PURPOSE

cursorqueryOptional

opaque offset cursor · nullableOpaque `offset-N` cursor returned by `next_cursor`; valid only with the same filters.EXAMPLEoffset-24

limitqueryOptional

integer · 1–200 · nullableMaximum public assets to return; defaults to 24.Schema range: 0 to unboundedEXAMPLE24

statusqueryOptional

canonical lifecycle state · max 32 · nullableOptional case-insensitive exact lifecycle-state filter.EXAMPLEPUBLISHED

asset_typequeryOptional

canonical asset classification · max 64 · nullableOptional case-insensitive exact asset classification filter.EXAMPLECERTIFICATE

qqueryOptional

string · 1–200 · nullableOptional case-insensitive search across UUID, name, symbol, and description; maximum 200 characters.EXAMPLEsolar

X-Request-IDheaderOptional

stringOptional caller correlation identifier. The gateway emits the effective value on the response.

RESPONSES

Status and payload examples

200Canonical resource projection.Read completed · JSON RESPONSE+

{
  "assets": [
    {
      "asset_type": "example-asset-type",
      "asset_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB",
      "base_currency": "USD",
      "collection_uuid": "01K4A7M4N8Y2Q6R9T3V5W7X1ZB",
      "created_at": "2026-09-02T18:30:00Z",
      "decimals": 0,
      "description": "example-description",
      "maximum_supply": "example-maximum-supply",
      "media_uri": "https://example.com/resource",
      "metadata_hash": "example-metadata-hash",
      "minted_supply": "example-minted-supply",
      "name": "example-name",
      "published_at": "2026-09-02T18:30:00Z",
      "status": "example-status",
      "symbol": "example-symbol",
      "updated_at": "2026-09-02T18:30:00Z"
    }
  ],
  "limit": 0,
  "next_cursor": "example-next-cursor"
}

INTEGRATION DECISION

CALLER ACTION: Accept the returned representation or receipt, then select one canonical identifier from the response and open its detail operation when the live contract exposes one.
RETRY SAFETY: For another page, send the returned opaque cursor unchanged with the same filters. Restart without a cursor when a new snapshot is required.
STATE RECONCILIATION: Use returned identifiers and versions as the comparison point for later reads. Refresh at the same network and finality point; compare height, block hash, transaction hash, canonical status, pagination cursor, and indexed-at timestamp.

422Path, query, or body validation failed.Request must change · JSON RESPONSE+

{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}

INTEGRATION DECISIONinvalid_credentials

CALLER ACTION: Rebuild the request from the live OpenAPI operation and correct the rejected method, media type, header, parameter, or body field.
RETRY SAFETY: Do not retry the same invalid request. A corrected read may be sent as a new attempt.
STATE RECONCILIATION: Compare the submitted values with the documented constraints before another call. Refresh at the same network and finality point; compare height, block hash, transaction hash, canonical status, pagination cursor, and indexed-at timestamp.
ESCALATE WHEN: Escalate when canonical hashes, heights, finality, or index freshness disagree with an authoritative node or when a reorganization exceeds policy.

502An authoritative dependency is unavailable; the gateway fails closed.Dependency unavailable or outcome uncertain · JSON RESPONSE+

{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}

INTEGRATION DECISIONinvalid_credentials

CALLER ACTION: Treat the failure as transient and preserve the last known good representation without presenting it as fresh.
RETRY SAFETY: Retry with bounded exponential backoff and jitter; stop after the integration's failure budget is exhausted.
STATE RECONCILIATION: Refresh at the same network and finality point; compare height, block hash, transaction hash, canonical status, pagination cursor, and indexed-at timestamp.
ESCALATE WHEN: Escalate when canonical hashes, heights, finality, or index freshness disagree with an authoritative node or when a reorganization exceeds policy.

503The authoritative service or read model is unavailable.Dependency unavailable or outcome uncertain · JSON RESPONSE+

{
  "code": "invalid_credentials",
  "message": "the supplied Hybrid credential is invalid"
}

INTEGRATION DECISIONinvalid_credentials

CALLER ACTION: Treat the failure as transient and preserve the last known good representation without presenting it as fresh.
RETRY SAFETY: Retry with bounded exponential backoff and jitter; stop after the integration's failure budget is exhausted.
STATE RECONCILIATION: Refresh at the same network and finality point; compare height, block hash, transaction hash, canonical status, pagination cursor, and indexed-at timestamp.
ESCALATE WHEN: Escalate when canonical hashes, heights, finality, or index freshness disagree with an authoritative node or when a reorganization exceeds policy.

OPERATIONAL NOTES

Security and lifecycle guarantees

EXPLORER: Assets through the canonical Hybrid-Chain V2 interface. Authoritative owner: asset-registry-read-model.
The Rust gateway validates the public contract and routes only to the authoritative owner; clients never address internal services directly.
The tables and examples are derived from the current gateway source OpenAPI. Re-fetch the deployed OpenAPI before execution; deployment status is shown separately on this page.
Only parameters present in the OpenAPI operation are accepted; undocumented query keys fail closed with HTTP 422.

Reference version and availability details

This route is implemented in canonical gateway source and appears in the production OpenAPI snapshot observed 2026-10-02T23:27:55.510Z. Authentication, tenant, feature, venue, and market policy still apply.

Verify the exact production OpenAPI operation Return to the V2 directory