Token, pair and venue pages: look up a route before you swap
Every listed token, its main pairs and every venue Tirio routes through have their own page, with contract addresses and a live indicative route.
Sometimes you want to know something before you connect a wallet. Which contract is the real CAKE? How would a BNB to USDT swap be routed right now? Which venues does Tirio actually use, and how does it price them? tirio.io now answers those questions on plain pages that anyone can open and share, no wallet needed.
There are three kinds: token pages, pair pages and venue pages.
Token pages
/token lists the tokens the Tirio API lists by default, about a hundred of them, and each one has its own page at /token/<symbol>, for example /token/cake. A token page shows:
- The contract address on BNB Chain and the token's decimals, with a link to the explorer. If you are about to paste an address into a wallet or a swap, this is a quick way to cross-check it against Tirio's list. Our token checklist explains why the address matters more than the symbol.
- An indicative price for one unit of the token in USDT (or in USDC for USDT itself), with the route Tirio would take: each path's share, every hop with its venue and pool fee, the price impact where it was measured, a network fee estimate and the block the pool state was read at.
- The pairs you can open, against BNB, USDT and USDC, plus buttons to swap the token or open its trade page.
Where a symbol is shared by several tokens, the page address uses the contract address instead of the symbol, so a link always points at exactly one contract.
Pair pages
A pair page lives at /swap/<from>/<to>, for example /swap/bnb/usdt. It shows:
- An indicative price for one unit of the first token with its full route, as on the token page.
- Both tokens' contract addresses and decimals.
- Three ways in: open the swap app with the pair already filled in, flip to the reverse pair, or open the pair on the trade page.
- Related pairs for the same tokens.
Pair pages exist for every listed token against BNB, USDT and USDC.
Venue pages
/dex lists every liquidity source Tirio routes through on BNB Chain, grouped by kind: constant-product AMMs, concentrated-liquidity pools, singleton pool managers such as Uniswap V4 and PancakeSwap Infinity, stable pools, on-chain market makers, launchpad curves and Tirio's own order book. Each venue has a page, for example /dex/pancakeswap-v3, with:
- What kind of venue it is, in a sentence.
- The contract Tirio reads it from, with an explorer link.
- How Tirio quotes it: with its own copy of the pool math for constant-product and concentrated-liquidity pools, or by asking the venue on chain where its pricing lives in the venue's own contract.
- The adapter id in the API, the value you pass to the API's
includeDexesorexcludeDexesparameters to route only through, or around, that venue.
Some venue pages carry a note of their own. The four.meme page, for example, explains that Tirio only buys on four.meme curves, because a token that has not graduated cannot be transferred outside four.meme's own contracts.
Reading one
The CAKE page is built from the API's indicative price for one CAKE in USDT. Here is that route as the API returned it when we checked on 2026-10-01, at block 125,117,808:
| Line | Value |
|---|---|
| Indicative price | 1 CAKE ≈ 2.5945 USDT |
| Route | 100 % through one PancakeSwap V3 pool with a 0.05 % fee |
| Price impact | 0 bps |
| Network fee estimate | 198,488 gas |
For one unit of a liquid token, a single deep pool is often the whole story, and the page says so plainly. For larger amounts the route can look very different, which is why the app quotes your exact amount when you open the swap. Our post on how aggregators split routes shows a 2,000 BNB order spread over eleven paths.
The block number links to the explorer, so you can see exactly which state of the chain the figures describe, and every hop names its pool, so you can open it and look for yourself.
What the numbers on these pages mean
The prices on token and pair pages are indicative. They are routed with the same engine as the app, but for a fixed amount of one unit, not your amount, and they are not simulated. They are shown before the 3 bps Tirio fee the app adds to swaps, and the pages refresh about every 30 minutes. The block number tells you exactly when the pools were read.
When you open the swap from one of these pages, the app quotes your actual amount live. The quote you sign is simulated as the complete transaction at the latest block, as every Tirio quote is. Our post on why every quote is simulated explains what that adds.
A few ways to use them
- Check a contract before you trade a token someone sent you a link for.
- Preview a route for a pair before connecting a wallet: which venues it uses, how it splits and what the price impact looks like for a small trade.
- Share a pair. A pair page is a stable link that opens straight into the swap with both tokens filled in.
- Find an adapter id to include or exclude a venue when you call the API.
- Learn how a venue is priced before you trust a route through it.
If the API cannot be reached at a given moment, the pages render without the live figures, and the swap app keeps working on its own.