Skip to main content
The Intents API is the integrator-facing interface for requesting quotes, submitting orders, and tracking status. All endpoints are open and require no API key.
For solver-facing endpoints (quote submission, account management), see the Solver API Overview. For authentication details, see Authentication.

Base URLs

Interactive API documentation is available at /docs on both environments.

Endpoints

Platform Differences

The quote and tracking journey is the same on every chain: request a V1 quote, sign and send the returned transaction, poll /orders/status. The differences are at the edges:
  • EVM: satisfy checks.allowances before sending; off-chain flows (gasless escrow, signed Compact claims) can instead go through POST /orders/submit. See Create and Submit Orders.
  • Tron: wrap the returned calldata in a TriggerSmartContract envelope; escrow settlement only. See Tron vs EVM.
  • Solana: rebuild the transaction template with the returned compute-unit limit and a fresh blockhash before signing; on-chain only — POST /orders/submit does not accept Solana orders. See Solana vs EVM.

Order Lifecycle

GET /orders/status reports one of four states:
Signed covers everything before a fill, including the on-chain Open event. If the order is not filled before fillDeadline, it can be refunded after expires, ending in Refunded. See Track Order Status for polling and the WebSocket status mapping.

Addresses

All endpoints take addresses as CAIP-2 chain id + native address pairs ({ "chain": "eip155:8453", "address": "0x…" }) — hex on EVM, base58 on Tron and Solana. No special encoding is required.

Amounts

All amounts are in the token’s smallest unit (wei-equivalent), with no decimals. For example, 1.5 USDC (6 decimals) is 1500000.

Next Steps

Request a Quote

Fetch solver pricing for your intent

Create and Submit Orders

Construct and submit an order to the solver network

Track Order Status

Monitor orders via the API or on-chain events

Solver API

Solver endpoints, quoting, and filling orders