Where It Fits
- You need the broadest coverage - assets, chains, and corridors beyond what any single liquidity source quotes, including the long tail the RFQ venue deliberately doesn’t chase
- You want ranked candidates with a recommendation rather than a single take-it-or-leave-it price
- You value failure isolation - one source being down, slow, or empty never suppresses valid candidates from the others
- You want one-signature cross-chain UX - the user expresses an intent and signs once; route selection, bridging, and settlement become the candidate’s problem, not the user’s
Quick Reference
The Trade Flow
Each candidate carries anexecutionMode telling you who puts the transaction on-chain. Preflight returns the exact nextActions for the candidate you selected.
- apiSubmit (native settlement)
- walletBroadcast (self-execution)
TetraFi submits the settlement transaction. Your user signs the order; TetraFi handles the rest.
Guarantees, Stated Per Candidate
The Router API never averages guarantees across sources. Every candidate in the response states its own terms, and the ranking compares them net of gas and explicit fees:
A candidate filled by the RFQ venue keeps RFQ-grade firmness; a multi-leg bridge route states its own settlement model. The product you called is still Router - the guarantees you rely on are the ones printed on the candidate, never implied by a source label.
Endpoint Map
POST /api/v1/quotes and /api/v1/orders/* remain available as documented temporary aliases for the Router namespace and emit deprecation metadata. New integrations should target /api/v1/router/*.Keep Going
Quickstart
A first candidate selected, signed, and settled - in one sitting.
Token Approvals
The allowance groundwork that makes settlement possible.