> For the complete documentation index, see [llms.txt](https://aboutcryptotalks.gitbook.io/aboutcrypto/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aboutcryptotalks.gitbook.io/aboutcrypto/aibai-bridge-route-types-and-when-each-fits.md).

# Aibai: Bridge Route Types and When Each Fits

Aibai bridges crypto between blockchains; the route to choose depends on what must arrive: an original token, a backed copy, or a different asset. To move funds, [Aibai](https://baibai.pro) takes a request on one network and arranges delivery on another, if that exact route is supported. Check the received token before approving.

### Which Aibai Route Fits the Token You Need?

The right route delivers the exact token your receiving wallet or app accepts. A matching ticker, or short token name, is not enough: check its contract, the code that records its balances.

* **Native token:** Best when the destination needs a token issued directly on that chain, such as USDT on Solana. Depending on the asset, a route may create new tokens there or pay from a stock already held there. It does not fit when that exact token is unavailable.
* **Wrapped token:** Best when you need an asset on a chain where the original does not exist. The bridge holds the original and issues a backed copy, called a wrapped token. It does not fit if the receiving app accepts only the original token.
* **Bridge and swap:** Best when you want to arrive with another asset, such as sending ETH and receiving USDT. The route also trades tokens, so the amount depends on the trade price and available funds, called liquidity. It does not fit if the quoted amount falls below what you need.

### How Does a Transfer Reach the Other Chain?

Your wallet sends tokens on the source chain, and a separate transaction delivers tokens on the destination chain. One bridge design holds the source tokens and creates a backed copy elsewhere. Another pays from tokens already held on the destination. The original coin never travels between the two blockchains.

Some routes first ask you to approve a smart contract, a program on the blockchain, to spend your tokens. That approval can be a separate paid transaction, so read its spending limit before signing. You also need enough of the source chain’s fee coin to pay gas, the network fee for processing transactions.

Save the source transaction ID until the destination balance appears. A source payment can succeed while delivery remains pending, especially when the bridge waits for finality. That means waiting until the source transaction is unlikely to be reversed. A shortage of payout tokens can also cause a delay.

### What Will It Cost, and What Should You Check?

Check the total cost, destination token, and destination network in the live quote before signing. Cost can include source gas, a bridge fee, destination costs, and a swap price difference. Check Aibai supported networks and token pairs together; support for a chain does not guarantee support for your token.

Say you send 1,000 USDT, pay $2 in source gas, and the quote deducts $3 in bridge fees plus $1 in destination costs. You spend 1,000 USDT and $2; 996 USDT arrives. That is about $6 in total cost if USDT stays near $1. Repeat the calculation with your own quote.

Transfer times vary by route, so follow the displayed estimate and check any minimum or maximum amount. Before a large transfer, check who controls tokens held by the bridge and whether its contracts can be paused. Confirm that the receiving wallet accepts the destination token’s contract; send a small test amount if you are unsure.

Choose by the token that must arrive, then compare the quoted payout, time, and bridge controls. Confirm the exact network and token contract before sending.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://aboutcryptotalks.gitbook.io/aboutcrypto/aibai-bridge-route-types-and-when-each-fits.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.