Skip to main content
A Routes quote can contain more than one step or intent. Read steps[] to understand what executes and which transaction delivers the final asset. Use the quote reference for complete request and response examples.

​
How to read a route

The quote schema distinguishes these intent roles:
  • local: an intent associated with the local execution leg.
  • bucket-candidate: one of several alternative intents; do not expect every candidate to execute.
  • stitched-destination: an intent for the final delivery leg of a composite route.
Inspect each intent’s decoded route and calls as well as its display metadata. A provider label alone does not identify every contract or token-transport mechanism used by the route.

​
Eco solver fill

A solver supplies destination tokens and executes the route through the destination Portal. The source vault releases the reward after the configured prover exposes valid fulfillment evidence. For a direct token delivery, check the destination chain, token, recipient, and transfer amount. This route can appear as a bridge step attributed to Eco.

​
Post-bridge swap

A route can deliver an intermediate token and swap it on the destination chain. The solver supplies the intermediate asset and the Executor executes the swap as destination calls. A bridge and swap step can refer to the same intent. The destination fulfillment is atomic within its transaction. The recipient and output constraint may be encoded inside swap calldata rather than a separate token-transfer call. Do not identify this shape solely from whether the requested token appears in a token list. Inspect the returned steps and route.

​
Pre-bridge swap

A route can first swap the source asset and use the result to fund a cross-chain leg. Candidate intents can represent alternative output amounts for that swap. The initial intent’s fulfillment may only complete the source-chain work. Track the selected bridge leg and the final delivery; do not treat every candidate as an outstanding transfer or assume the source swap’s completion proves receipt on the destination.

​
Third-party routing over CCTP

A route can include Circle CCTP calls to burn USDC on one chain and mint it on another. Recognize a burn from the actual target contract and decoded depositForBurn call, including the destination domain and mint recipient. CCTP requires an attestation and a destination-chain message submission to complete the mint. A source-chain intent that executes the burn can be fulfilled before the destination mint occurs. Its fulfillment status alone does not prove delivery. CCTP token transport and an Eco prover are separate parts of a route. Circle Gateway deposit flows are also a separate integration; see Circle Gateway deposits.

​
Same-chain swap

A same-chain route has the same source and destination chain. Its intent can execute a swap and transfer the output within one transaction. Inspect the route’s prover and execution instructions to determine how it is fulfilled; a same-chain quote does not by itself establish use of flashFulfill.

​
Verify and track

  1. Verify the quote signature and all signed intent hashes using Quote verification.
  2. Check the executable route’s chains, assets, recipient, output constraints, and expiry before funding.
  3. Fund using the returned execution instructions.
  4. Track the quote and relevant intents through intent status.
  5. Confirm the final delivery transaction or destination balance before marking a composite transfer complete.
An unknown step type or role needs explicit handling. Avoid silently interpreting it as a direct transfer. A quote’s timing estimates and historical example amounts are not fixed properties of the route.

​
Next steps