Developers

Bridge into Sui.

Create a route from supported source chains and deliver USDsui or SUI to any Sui address. Your user signs the source payment. Talise tracks delivery and handles the optional Sui conversion.

Request an API key Open Talise Bridge

GET/chainsAvailable source networks and route freshness
GET/tokens?chainId=8453Tokens and base-unit decimals for a source network
POST/quotesPreview price only; no payment instructions
POST/routesCreate a live route and return source payment instructions
GET/routes/{id}Read source and delivery status
POST/routes/{id}/completeAdvance a route that needs Sui conversion

For coding agents

Give your agent the integration skill.

It covers route creation, wallet signing, delivery status, and the checks that keep a transfer from being sent twice. Your API key stays on your server.

Open agent skill OpenAPI spec

Prompt: “Read https://bridge.talise.io/bridge-api/SKILL.md and integrate Talise Bridge into my app.”

mkdir -p .agents/skills/talise-bridge && curl -fsSL https://bridge.talise.io/bridge-api/SKILL.md -o .agents/skills/talise-bridge/SKILL.md

Get started

Use /chains and /tokens to discover live coverage. Amounts are token base units: 10 USDC is 10000000. Request a key, then call /quotes to preview and /routes to create a live route.

Keep the API key on your server. Sign the returned source transaction in the user’s wallet. For deposit-address networks, send the exact source.depositAmount and memo. A Solana route includes a separate 1% fee payment; submit both Solana transfers in one source transaction.

A live route needs a unique Idempotency-Key. Retry with the same key if creation times out. Never send funds twice while a route is pending. Poll /routes/{id}; the Sui conversion also runs through Talise’s relay, and /complete can advance it.

Example · Base USDC to USDsui

curl -X POST https://bridge.talise.io/api/v1/bridge/routes \
  -H 'Authorization: Bearer tb_live_YOUR_KEY' \
  -H 'Idempotency-Key: your-unique-order-id-0001' \
  -H 'Content-Type: application/json' \
  -d '{
    "chainId": 8453,
    "token": "TOKEN_ADDRESS_FROM_CATALOGUE",
    "amount": "10000000",
    "sender": "0xYOUR_EVM_WALLET",
    "recipient": "0xYOUR_SUI_WALLET",
    "receive": "USDsui"
  }'

Response and limits

The route response includes id, expiresAt, estimate, fees, source.transaction or source.depositAddress, and the Sui recipient. Estimates include provider pricing and can change until the source transaction settles. GET /routes/{id} reports awaiting_source_transaction, converting, delivered, or needs_attention, plus transaction hashes where available.

Live route creation is limited to 10 requests per minute and 200 per day per partner; quotes to 30 per minute and 1,000 per day. A 429 includes Retry-After. Routes are one way into Sui. A key is required for quotes and live routes. Catalogue endpoints are public.

OpenAPI specification