---
title: "GET /supported-assets"
method: GET
path: "/supported-assets"
tags: ["assets"]
---

# GET /supported-assets

`GET /supported-assets`

Lists the assets supported by the Tenbin platform. Returns the same catalogue on every deployment, regardless of which asset this pod serves — use it to discover newly launched assets without a code change.

The `asset` field is the value to use as the `{asset}` path segment of the per-asset API base URL `api.tenbin.xyz/{asset}` — the lowercase token ticker, e.g. `tgld` → `api.tenbin.xyz/tgld`.

**Market-maker onboarding flow:**

1. `GET api.tenbin.xyz/{asset}/supported-assets` — list every supported `asset`.
2. For each, `GET api.tenbin.xyz/{asset}/deployment` — fetch that asset's contract addresses (`controller`, `domain_separator`, `collateral`, `token`, `staked_token`) needed to quote and submit orders.

Each entry also carries the asset's mainnet `controller` address here as a convenience (the EIP-712 verifying contract for order submission); the full, environment-correct contract set is served by `/deployment`.

## Response `200`

Supported assets

- SupportedAsset[]
  - `asset` string, required — The `{asset}` path segment of the per-asset API base URL `api.tenbin.xyz/{asset}` — the lowercase token ticker (e.g. `tgld`). Mirrors the asset namespace's public ingress `pathPrefix`.
  - `controller` string, required — Mainnet address of the asset's `Controller` contract — the EIP-712 verifying contract that signed orders are submitted against.
  - `name` string, required — Human-readable display name (e.g. `Tenbin Gold`).
  - `symbol` string, required — Token ticker symbol (e.g. `tGLD`).

---

[API](https://skmtc.net/tenbinlabs/apis/order-service-api.md) · [All operations](https://skmtc.net/tenbinlabs/apis/order-service-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/tenbinlabs/order-service-api/revisions/d8ed26b0f13c/schema)