Engines, normalization, scoring, and strategies.
Engines fetch candidates. They do not decide “the winner”.
Output-first.
Searches deeper. Optimizes for best output.
Speed-first.
Prefers simpler paths. Optimizes for fast settlement.
Safety-first.
Strong health and reliability gating. Optimizes for execution certainty.
All engines return the same route object. This keeps clients provider-agnostic.
For the canonical shape, see Route object schema.
Scoring is deterministic. Same inputs produce the same ranking.
Scoring is based on dimensions like output, fees, time, and reliability. See Scoring and strategies for the dimensions and formula.
Strategy changes weights only. It does not change engine behavior.
Practical rule:
use balanced as a default
balanced
use safest for large amounts
safest
use fastest when time is the primary constraint
fastest
Avoid mapping “strategy = engine”.
Strategy is a scoring preference. Engines are candidate sources.
Last updated 2 hours ago
