> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stabyl.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Supported Wallet Routes

> Supported blockchain route families and how to discover current availability.

Use `GET /partner/wallets/chains` as the source of truth for route availability. Please note that route availability might change without notice, do not hardcode route availability in production systems.

| Family | Production              | Staging/Test     |
| ------ | ----------------------- | ---------------- |
| EVM    | Base, BSC, Arbitrum One | Ethereum Sepolia |
| Tron   | Tron                    | Tron Nile        |
| Solana | Solana mainnet          | Solana testnet   |

## Required Headers

`GET /partner/wallets/chains` is public. Other wallet routes require `X-Api-Key`.

## Common Failures

| Status | Meaning                                       |
| ------ | --------------------------------------------- |
| `400`  | Unsupported or malformed chain parameter      |
| `401`  | Missing API key on authenticated wallet route |
| `404`  | Requested route is not available              |

## Route Selection

Use the returned chain identifiers directly in `GET /partner/wallets/crypto/address`. Route families can share asset symbols, so the chain value is part of the deposit instruction and must be stored with the address.

For example, `USDT` on Tron and `USDT` on an EVM chain are different deposit routes. Showing the wrong route can cause funds to be sent to an address that does not match the user's intended network.

Refresh route metadata periodically and before showing deposit instructions in your application.