Skip to main content
These optional discovery endpoints return metadata for the chains and tokens Trustware discovers from its upstream liquidity providers. Use them to populate chain and token selectors in your UI rather than hardcoding assets. They are not required for the core integration flow. Discovery coverage is broader than confirmed routing support. See the caveat under /chains below, and confirm a destination with a quote call before relying on it.

GET /chains

GET https://api.trustware.io/api/v1/routes/chains Returns metadata for every chain discovered from upstream providers, including chain ID, name, type, native currency, RPC URL, block explorer URLs, and the providers available for that chain.
This list reflects raw upstream liquidity coverage. It is not a guarantee that every entry is routable as a destination. The Cosmos family is the widest gap: many Cosmos chains appear in this response, and Nibiru (cataclysm-1) is the Cosmos destination with end-to-end support. Treat the remaining Cosmos entries, and the sui-mainnet entry, as informational, and confirm a destination with a quote call before building against it.Sei has two identifiers, and only one of them appears here. Sei EVM is returned as chain ID 1329. Sei-Cosmos (pacific-1) is still recognized by token discovery and by the SDK’s address validation, but is currently absent from this endpoint, so use 1329 unless you have confirmed a pacific-1 route with a quote call.

Response

Chain object fields


GET /tokens

GET https://api.trustware.io/api/v1/routes/tokens Returns tokens supported by Trustware. Called with no query parameters, it returns the full unpaginated list. Passing any of the optional query parameters below switches the endpoint into paginated mode and the response shape changes accordingly.

Query parameters

Pagination activates as soon as any of these query parameters is present. Call with no query string to receive the full token list in a single response.

Response

Token object fields