Skip to main content

​
Step 1: Account Creation & Identity

Currently, solver identity is managed through a standalone dashboard.
  1. Register: Go to the Solver UI: intents.li.fi (or devintents.li.fi for testnet).
  2. Set Identity: Choose a Solver Name. This is a permanent identifier used for your API keys and reputation tracking.
  3. Generate API Keys: Create an API key in the dashboard. You will need this to submit quotes to the /quotes/submit endpoint.

​
Step 2: Address Registration

You must prove ownership of the wallet addresses you will use to fill intents.
  1. Fetch Message: Get a one-time registration message from GET /api/v1/solver/register/message.
  2. Sign Message: Sign it with your solver account’s key — ECDSA or EIP-1271 on EVM, ed25519 on Solana.
  3. Submit Pairing: Send the account, chain, message, and signature to POST /api/v1/solver/register.
See Registering Accounts for code examples.
Each address can only be tied to one API key. If your solver cannot sign messages, the LI.FI team can add a solver address for you.

​
Step 3: Prove execution on mainnet with exclusiveFor

Before being whitelisted for the LI.FI API, you must prove your execution logic works on mainnet. You can test using either the Lintent UI or the LI.FI Intents MCP Server — both are equally valid approaches.

​
Manual Testing via Lintent

  1. Open Lintent: Go to lintent.org.
  2. Configure Intent: Set up a swap/bridge intent. Use “Escrow” input instead of “The Compact”.
  3. Set Exclusivity: Manually enter your registered solver address into the exclusiveFor field. This ensures only your solver can fill this specific intent.
  4. Execute: Submit the intent and verify that your solver receives the resulting order, fills it, and settles.
Lintent UI showing the exclusiveFor field

Lintent UI with the exclusiveFor field set to your solver address

​
Testing a Solana order

For Solana, request a V1 quote, add the returned compute-unit limit, replace the dummy blockhash, and sign and send the rebuilt transaction. The resulting OpenEvent is ingested and broadcast to your solver. See Opening on Solana for the transaction code. For a Solana-origin test, set exclusiveFor to the base58 Solana public key that will sign finalise, including when the output is on EVM. Complete the entire solver path—not only order ingestion—using the Solana execution checklist: fill, prove or receive the attestation, and finalize before expiry.