LI.FI toAmount fee probe

/quote/toAmount is minimum-output quoting, not deterministic invoice settlement

This page reproduces Adam’s case: the recipient wants 1 USDC, while the request also includes a 1% integrator fee and a 0.5% tenant/distribution fee. The REST probe shows LI.FI grossing up the input so estimate.toAmountMinmeets the requested amount. The final estimated output can still be higher than the requested display amount.

Test inputs

Defaults use a compact public Polygon USDC → USDC.e route. Change these values to test another partner path.

fromChainPolygon = 137toChainPolygon = 137fromTokenPolygon native USDCtoTokenPolygon bridged USDC.erequested toAmount1 USDC = 1000000 unitsintegratorregistered demo integratorintegrator fee0.01 = 1%distribution fee0.005 = 0.5%distribution receiverEVM fee receiverslippage0.003 = 0.3%fromAddressplaceholder sendertoAddressplaceholder recipient

Interpretation

Correct partner-safe wording: use /quote/toAmount when the recipient must receive at least the requested amount after fees. The sender pays the grossed-up input.

Do not overclaim: this is not “the final settled amount will equal exactly 1 USDC”. The route can estimate more than the target, and execution still depends on slippage and market movement.

Small point on /quote/toAmount: because of slippage protection, the received amount can be a bit higher than requested — for example, not 100% identical to exactly 1.000000 USDC. In normal swap/bridge UX this is usually accepted by users as positive slippage. If your business requires a 100% identical output amount, evaluate LI.FI Intents instead: see the request quote docs and the online Intents demo.

SDK check: @lifi/[email protected]+ supports getQuote({ toAmount }). This repo pins @lifi/[email protected] for the probe.

Known SDK caveat: distributionFees is typed, but SDK quote serialization still sends object arrays incorrectly in 4.0.1. Raw REST bracket encoding works.

Result

Run one of the probes above. The summarized quote and raw response will appear here.