Skip to main content
Solve RFQ covers the two ways to get an executable price out of Sprinter.
Default to LI.FI Intents. It is the path that draws on Sprinter Liquidity, which is what makes an instant fill at a promised price possible. Reach for the Swap API when the pair is not onboarded with Sprinter, or as a fallback when a quote does not return.

LI.FI Intents

Two calls. The first prices the order and holds the liquidity; the second turns that into a transaction the user signs.
Authenticate the RFQ call with your API key in the X-Auth-Token header. The transaction call carries the quote itself, so it needs no header. The responses follow LI.FI’s own intents API shapes, with one difference worth coding for: when Sprinter cannot serve a request it returns 404, not a 200 with an empty quotes array.
Quotes only return for assets Sprinter has onboarded — underwritten, allocated liquidity to, and configured routes for. See the Asset Issuer quickstart for what onboarding involves.

Swap API

Route a swap against public on-chain liquidity and get back executable call data. No onboarding, no reservation, no firm price. See the Swap API overview for base URLs, authentication, and the response format.

Not this: the Liquidity API

Sprinter Liquidity exposes the borrow-quote and signing endpoints directly. That surface is for crosschain solvers running their own fill infrastructure — it hands you a borrow authorization, not a transaction, and expects you to settle the intent yourself. If you are an asset issuer, wallet, or application asking Sprinter for a price, use LI.FI Intents. The RFQ endpoint runs the same pricing and reservation pipeline and returns something you can sign.