Skip to main content
Stablecoin conversions let you move value between USD and stablecoins, and move a stablecoin across chains, all through the same security model that governs the rest of your assets. Every conversion runs through one endpoint—the asset pair you choose sets the direction.
Testing: Examples use the staging host https://api.anchorage-staging.com and "USD_R" for USD-side legs. In production, use https://api.anchorage.com and "USD".

​
Start here

  • Mint — Convert USD into a stablecoin. See Mint.
  • Redeem (burn) — Convert a stablecoin back to USD. See Redeem.
  • Bridge — Move a stablecoin between chains. See Bridge across chains.

​
The mental model

All three operations call the same endpoint, POST /v2/stablecoins/conversion. The sourceAssetType and destinationAssetType you pass set what happens:
  • Mint converts USD into a stablecoin (sourceAssetType: USD, destinationAssetType: <stablecoin>).
  • Redeem (burn) converts a stablecoin back to USD (sourceAssetType: <stablecoin>, destinationAssetType: USD).
  • Bridge moves a stablecoin between chains—sourceAssetType and destinationAssetType are the same stablecoin on different chains (for example, USDX_BSC_T → USDX_HOODI). Internally, a bridge runs a burn on the source chain and a mint on the destination chain through a shared reserve.
For the full comparison and the request fields they share, see Convert stablecoins.

​
Action availability

/v2/stablecoins/history may return records with operationType: SWAP once stablecoin swaps go live. Treat unknown operationType and status values as a forward-compatibility fallback, not an error.

​
Before you convert: prerequisites

Identify the wallets and asset types involved, then confirm the API key has the right permission and authentication. See Set up.
Stablecoin conversion and history endpoints require only the Api-Access-Key header—no Api-Signature or Api-Timestamp.