Skip to content

docs: add LI.FI Intents endpoints under a Solve RFQ section - #222

Open
alexmmueller wants to merge 5 commits into
mainfrom
docs/221-lifi-intents-endpoints
Open

docs: add LI.FI Intents endpoints under a Solve RFQ section#222
alexmmueller wants to merge 5 commits into
mainfrom
docs/221-lifi-intents-endpoints

Conversation

@alexmmueller

@alexmmuelleralexmmueller commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Closes#221

Documents the LI.FI Intents endpoints and reorganizes the docs around them.

Acceptance criteria

  • Integrator flows use /lifi-intents/rfq instead of the Liquidity API
  • New "Solve RFQ" API-reference section merging Swaps + LI.FI Intents, explaining when to use which
  • Downstream examples fixed — asset issuer, redemption liquidity

Changes

  • OpenAPI/lifi-intents/rfq and /lifi-intents/transaction plus their schemas, converted from sprinter-api's Swagger 2.0
  • API reference — two endpoint pages and a section overview; "Swaps" regrouped under "Solve RFQ" (nav-only, existing URLs preserved)
  • Asset-issuer quickstart — rebuilt around RFQ → transaction → send; Sprinter now builds the exclusive limit order, so that step is gone
  • Liquidity sectionredemption-liquidity merged into the quickstart and contracts deleted, both redirected
  • New pages/pricing (shared vs dedicated facility) and /solve-rfq (concept)
  • Glossary — Exclusive Fill, Intent, Solve RFQ

Notes for review

  • POST /lifi-intents/transaction is unauthenticated. Documented as-is; worth a separate look, since the reservation re-key it performs has no solver check either.
  • The escrow address and data blob in the transaction response example are placeholders.
  • Verified with mint dev: nav resolves, no orphaned pages, no broken links or anchors, all pages render. Note the CLI needs Node LTS — it refuses Node 25+.

🤖 Generated with Claude Code

alexmmuellerand others added 5 commits August 6, 2026 10:18
Adds /lifi-intents/rfq and /lifi-intents/transaction to the OpenAPI spec
and documents both, then regroups the API reference so the new intents
calls and the existing Swap API sit under one 'Solve RFQ' section with
guidance on when to use which.
Nav-only regrouping — existing api-reference/solve/* paths are unchanged
so published URLs keep working.
Refs #221
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Rewrites the asset-issuer runtime flow around GET /lifi-intents/rfq and
POST /lifi-intents/transaction, replacing the manual borrow-quote plus
build-your-own-intent sequence. Sprinter now constructs the exclusive
limit order, so the integrator no longer sets the filler address.
Marks the Liquidity API overview as the solver-facing surface and points
integrators at Solve RFQ.
Refs #221
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Merges Redemption & Subscription Liquidity into the Asset Issuer
quickstart and deletes it — the two pages split one audience across a
product section and a quickstart, and duplicated the underwriting
criteria as 'What you submit' and 'Underwriting'. Those are now one
table. Pricing and the facility-vs-solver models move across as
reference sections below the runtime flow.
Deletes the Liquidity contracts page.
Reframes the Sprinter Liquidity overview around the two access paths,
with LI.FI Intents first for issuers/wallets/apps and the Liquidity API
for solvers, replacing a closing line that pointed only at the solver
guide.
Adds redirects for both deleted URLs.
Refs #221
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Adds /pricing as its own nav group, covering the two ways to access
Sprinter credit: shared liquidity drawn just-in-time from the general
pool, and a dedicated underwritten facility.
The dedicated facility follows the structure used in the OpenEden
integration overview — facility parameters, capital management,
replenishment against the settlement cycle, and commercials including
the minimum return on committed capital. Terms are presented as the
shape of what gets specified per facility; no counterparty's negotiated
figures are published.
Lifts the pricing and integration-model sections out of the Asset Issuer
quickstart, which now links here instead.
Refs #221
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Every API-tab group had a Documentation-side counterpart except Solve
RFQ, so a reader browsing the nav saw only the Liquidity API and
concluded that was the product. Adds /solve-rfq under Sprinter
Liquidity: concept only, no endpoints or schemas, covering why the
quote is firm (underwritten capital, reserved at quote time, exclusive
fill), the two consumer paths, and what it is not.
Replaces the access table in the liquidity overview with a pointer so
the comparison is single-sourced.
Adds Exclusive Fill, Intent and Solve RFQ to the glossary, which
defined Borrow Quote but nothing on the RFQ side.
Refs #221
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@alexmmueller
alexmmueller marked this pull request as ready for review August 6, 2026 12:21
Sending that transaction escrows the inputs on the origin chain and broadcasts the order to solvers.

<Warning>
Include the `quoteId` from the RFQ response. Without it the endpoint still returns valid calldata, but **no liquidity is reserved** and the order is not guaranteed a Sprinter fill — you get no error saying so.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similar to the /rfq endpoint ( quote) , we should mention here, visible the reservation time. It is 60 seconds. For an existing rfq quoteId the new reservation will be refreshed to 60 seconds from NOW when using in /transaction or directly 60 seconds from now if not used with a quoteId. Also keep in mind that this behavior is shared among pool with other solvers ... so if someone plays with /transaction for testing purpose it can reserve a lot of liquidity for 60 seconds

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add lifi intents endpoints to the docs

2 participants

@alexmmueller@LyonSsS