Pay
Send value over a supported route.
Receive
Receive value over a supported route.
Exchange
Trade between supported assets and markets.
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 Execution 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.
Applications can offer more than one route for the same outcome; reversing
a route reverses the outcome, as the table above shows.
Start Building
Integrate Lightning
Add supported Lightning payment routes to an application.
Exchange Assets
Exchange BTC and other assets, with both sides settling through Arkade.
Provide Liquidity
Provide pricing and liquidity for supported asset and payment routes.
Protocol Reference
Implement discovery, RFQ, settlement, and recovery.