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

> ## Agent Instructions
> SODAX is mainnet-only (no testnet chains or RPC endpoints exist) with a hub-and-spoke architecture; Sonic is the hub. SODAX is non-custodial protocol/software: it routes and settles; independent solvers on the marketplace fill — never say 'our solver', 'the SODAX solver', that SODAX trades, takes custody, or fills orders. For frontend/React integrations, prefer @sodax/dapp-kit hooks over calling @sodax/sdk directly. SDK operations — the methods that build, submit or await a transaction, and the API/quote calls — return Result<T, E> ({ ok: true, value } or { ok: false, error }): check result.ok, never wrap them in try/catch or branch on error.message; discriminate on the narrow error.code union instead. Synchronous config getters (getPartnerFee, getSupportedSwapTokens, getVault, ...) return their value directly, not a Result.

# Polygon: Networks & Assets

> What is live on Polygon today, and the networks and assets your users can reach from it.

Polygon is a spoke network in the SODAX System. User funds stay on Polygon; the hub (Sonic) coordinates execution, and solvers settle against deep native liquidity on each network rather than isolated bridge pools.

There are two asset lists to keep straight, and the difference is the point of SODAX:

* **Assets on Polygon**: the <span data-sodax-config="count" data-metric="chain-swap-tokens" data-chain="0x89.polygon">8</span> assets that live on Polygon itself, POL and ERC-20 tokens. These are what your users hold, send, and receive on Polygon; the entry and exit points of any Polygon-side flow.
* **Assets across the SODAX System**: <span data-sodax-config="count" data-metric="swap-tokens">166</span> assets across all supported networks. Every one of them is a valid swap destination or collateral source for your Polygon users, because every SODAX action is cross-network by default.

A user holding POL is not limited to the Polygon-side list. They can swap it into ETH on Ethereum, USDC on Base, SOL on Solana, or any other listed asset on any network, in one signed transaction. The on-Polygon assets are simply where those journeys start and end on your side.

Every count and list below is read live from the backend config API, `GET https://api.sodax.com/v2/be/config/all`, so it reflects what the backend serves today rather than what an SDK release has listed.

## Assets on Polygon

Live for swaps on Polygon:

<div data-sodax-config="swap-tokens" data-chain="0x89.polygon">
  Live token list loads from the config API. If it has not appeared, read `config.swaps.supportedTokens["0x89.polygon"]` from [`GET /v2/be/config/all`](https://api.sodax.com/v2/be/config/all), or use the SDK call below.
</div>

Live in the [Money Market](/polygon/money-market) for supply, borrow, repay, and withdraw:

<div data-sodax-config="money-market-tokens" data-chain="0x89.polygon">
  Live token list loads from the config API: `config.moneyMarket.supportedTokens["0x89.polygon"]` in [`GET /v2/be/config/all`](https://api.sodax.com/v2/be/config/all).
</div>

The two lists overlap but differ: some tokens are swap-only and some are money-market-only, so check the list for the action you are building.

Addresses are standard ERC-20 contract addresses on Polygon; POL, the native gas token, uses the zero address and is listed as `POL`. Match tokens by address rather than by on-chain symbol:

* **USDC.** Two Polygon contracts report the symbol `USDC`. The SODAX one is Circle's native USDC, the address Circle lists for [Polygon PoS](https://developers.circle.com/stablecoins/usdc-contract-addresses). The older bridged token, named `USD Coin (PoS)` on-chain, is not supported.
* **USDT.** The token SODAX lists as `USDT` reports the symbol `USDT0` on-chain. Look it up as `USDT` in the SODAX list.

Hub vault addresses per asset are listed in [Swaps: Compatible Assets](/developers/deployments/swaps-compatible-assets).

## Assets your users can reach

From a Polygon-sourced action, users can trade, lend, and borrow across every SODAX-supported network:

<div data-sodax-config="chains">
  Live network list loads from the config API: `config.chains` in [`GET /v2/be/config/all`](https://api.sodax.com/v2/be/config/all).
</div>

Chain identifiers come from `ChainKeys.*` in the SDK (`ChainKeys.POLYGON_MAINNET` = `'0x89.polygon'`), and the live chain list from `sodax.config.getSupportedSpokeChains()`. Prefer the config call over hard-coding: networks are added over time.

## Asset discovery in code

Never hard-code token addresses or asset lists; read them from the SDK config at runtime:

```typescript theme={null}
import { Sodax, ChainKeys } from '@sodax/sdk';

const sodax = new Sodax({
  chains: {
    [ChainKeys.POLYGON_MAINNET]: { rpcUrl: 'https://polygon.drpc.org' }, // not the packaged default
  },
});

// Swappable assets on Polygon
const swapTokens = sodax.swaps.getSupportedSwapTokensByChainId(ChainKeys.POLYGON_MAINNET);

// Money market assets on Polygon
const mmTokens = sodax.moneyMarket.getSupportedTokensByChainId(ChainKeys.POLYGON_MAINNET);
```

These lists ship with the SDK package, so a token the backend has added since your SDK release appears in the live tables above before it appears here.

***

* All deployment addresses by network: [Mainnet Deployments](/developers/deployments/mainnet)
* The full cross-network asset directory: [sodax.com/partners/asset-directory](https://sodax.com/partners/asset-directory)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.