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
Order Lifecycle
Orders can include transitional states depending on submission path and indexing timing. In most integrations, the primary execution progression is:
If the order is not filled before
fillDeadline, it can be refunded after expires.
Interoperable Addresses
The Intents API uses EIP-7930 interoperable addresses, which encode both the chain and address in a single bytes field. This applies touser, asset, and receiver fields in quote requests. The example below is an EVM address (ChainType 0x0000); non-EVM chains use their own CAIP-2 namespace. For Tron, the V1 endpoint takes native base58 addresses and avoids EIP-7930 hand-encoding entirely.
Example encoding of 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base (chain ID 8453):
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

