Skip to main content
Arkade Intents is a developer preview. On mainnet, Lightning send and receive go to one pinned solver within its card’s bounds. Developer Preview has the runnable flows as code.
Lightning invoice payment and asset exchange windowsLightning invoice payment and asset exchange windows
Arkade Intents gives applications a common way for users to pay, receive, and exchange value. An Arkade Intent records the result and constraints a user approves. The application presents available routes and terms, and a swap settles the selected route.

Understand Intents

How a quote sets the terms, and which contract settles each route.

Build with Intents

Add Lightning, onchain, and asset swaps to an Arkade wallet.

Earn Fees

Run a solver that prices and fills swaps.

​
What Works Today

Support varies by route. See Implementation Status for SDK support and current route limitations.

​
Why Intents

One market interface

Add compatible solvers without rebuilding the product around a new API.

Independent liquidity

Let more than one solver serve a market or route under shared rules.

Product control

Choose discovery sources, solver policy, presentation, and recovery UX.

​
How Routes Execute

Every route follows the same quote-first flow: intent, quote, fund, fill. Only the settlement contract depends on where the endpoints settle. Markets and Quotes covers the model and the contract split.

​
Routes and Corridors

A route is the directional path that can deliver a result. Its source and destination endpoints are written as <corridor>:<asset>, where the corridor identifies the settlement environment. A swap executes that route. The Arkade Intents Protocol covers discovery, RFQ, settlement, and recovery. Applications can offer more than one route for the same outcome; reversing a route reverses the outcome, as the table above shows.