Supported endpoints
How presets are applied
- LI.FI loads the preset defaults.
- LI.FI merges your request options on top of those defaults.
- Any conflicting keys fall back to the values you provided in the request body or query string.
Processing flow
- Validate that the requested preset name is present and active.
- Load the preset configuration (defaults, tool preferences, etc) or use the built-in default if it isn’t available.
- Merge preset defaults into the request payload or query parameters.
- Apply user-provided overrides so explicit values win.
- Log the resolved preset for observability and troubleshooting.
400.
Preset names
Presets can be referenced by:- Generic names such as
stablecoin - Specific names such as
stablecoin-cheapest
stablecoin resolves to stablecoin-cheapest by default. LI.FI may promote other presets behind the same generic name when new configurations such as stablecoin-fastest or partner-specific variants stablecoin-partnerX become available.
Using the preset parameter
Advanced Routes
Provide the preset inside theoptions object.
Quote
Send the preset as a query parameter.Available presets
- Stablecoin preset
- Commerce preset (coming soon)

