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

# Ranking

> How the best route is chosen.

## Compared in the asset's own units

Quotes on one pair are ranked on net output in atomic units, after every venue fee and the platform fee. For an exact-output trade the ranking is on net input. No price feed is used to compare two venues, so a stale price source cannot change the winner.

Each row carries the numbers the ranking used: `amountOutAtomic`, `minAmountOutAtomic`, `fees`, `feeBps` and `tierSavedBps`.

## Only executable routes win

A row is eligible when the venue serves the corridor and asset, its catalog is fresh, and the amount is inside its limits. It is executable when the venue can also produce something the wallet can sign for that source chain.

`best` is the highest-ranked row that is both. A row that can be priced but not signed stays in the table at its real score with `executable: false`.

## Two named picks

| Field         | Is                                                                      |
| ------------- | ----------------------------------------------------------------------- |
| `bestByPrice` | The `quoteId` of `best`.                                                |
| `bestByTime`  | The `quoteId` of the executable row with the lowest `estimatedSeconds`. |

Speed is never a tiebreak on price. A venue that publishes no ETA is not a candidate for `bestByTime`; `null` there means "not stated", not "instant". Both picks are `null` when nothing in the table is executable.

## Venue state is kept fresh

Each venue's chains, assets, corridors and limits are refreshed continuously, so a quote never waits on them. A venue whose state has gone stale, or which is failing, is left out of the table until it recovers rather than priced on limits that may no longer exist.

## Large orders

The same venue can pay best on a small order and worst on a large one. Above a per-asset size, the quote also measures how each venue's price moves with size. When splitting across venues would beat the best single route, the response carries a `splitPlan` describing that allocation and its `improvementBps`; `planReason` says why none is offered. The table itself, and what `build` executes, is unchanged.