> For the complete documentation index, see [llms.txt](https://docs.nexus.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexus.xyz/api-reference/bridge/get-bridge-assets.md).

# GET /api/v1/bridge/assets

List bridgeable chains and assets.

`operationId`: `getBridgeAssets`

**Authentication:** `hmacAuth`.

Returns the supported chains and, per chain, the depositable assets (USDC, USDX) with their decimals, minimum amount and required confirmations, and the withdrawable assets (USDX) with their minimum amount and flat fee. Metadata only — it moves no funds and reads no account state, but carries the standard `/v1/bridge` HMAC auth like the rest of the surface.

Asset scope is USDC and USDX; USDT is out of scope for this cut. `chain_id` is the serving network's numbered chain (`1` on mainnet, `11155111`/Sepolia on testnet) and is `null` on a local instance that serves no numbered chain. Arbitrum becomes another `chains[]` entry later with no shape change.

The published `min_amount` is provisional: the delivered-amount minimum is still being reconciled against the provider's quoted limits (ENG-8297), because a fixed-input funding route can deliver net of fees below a quote-time minimum. Treat it as a floor that may rise, not a settled figure.

## Responses

| Status | Body                                                                            | Meaning                                                    |
| ------ | ------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| `200`  | [`BridgeAssetsResponse`](/api-reference/guides/schemas.md#bridgeassetsresponse) | Supported bridge chains and their deposit/withdraw assets. |
| `401`  | — *(no schema declared)*                                                        | —                                                          |
| `429`  | — *(no schema declared)*                                                        | —                                                          |

## Example

```bash
curl -X GET 'https://exchange.nexus.xyz/api/exchange/api/v1/bridge/assets' \
  -H 'X-API-Key: nx_7f3a1b...' \
  -H 'X-Timestamp: 1776033911836' \
  -H 'X-Signature: <hmac-sha256>'
```

***

<sub>Generated from</sub> <sub></sub><sub>`eng/apps/exchange/api/openapi.json`</sub> <sub></sub><sub>(spec</sub> <sub></sub><sub>`0.9.27`</sub><sub>). Do not edit by hand — regenerate with</sub> <sub></sub><sub>`python3 product/docs/tools/api-reference/generate.py`</sub><sub>. Hand-authored context lives in the Guides pages.</sub>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nexus.xyz/api-reference/bridge/get-bridge-assets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.