Skip to main content

Access

The Routes API v1 requires x-api-key for quotes, funding submissions, status, chains, and tokens. Circle Gateway endpoints have separate access rules. See API access and conventions.
Contact Eco for API keys and integration questions. Sauce access uses partners@eco.com. See Get set up.
Check the environment, header, and key permissions. Use the returned status and error body to distinguish a missing key, invalid key, or attribution failure. See Errors and retries.

Transfers

Timing depends on the route, liquidity, source-chain confirmation, and any bridge or prover involved. A quote can include steps[].estimatedDurationSec; treat it as an estimate. Track the transfer through intent status.
Its reward can become refundable under the deadline and proof conditions. A refund requires a transaction; an expired or refundable status does not establish that funds have returned. See Vaults and resource locks.
It means that intent’s route was fulfilled. On a composite route, an intermediate intent can execute a source swap or CCTP burn before final delivery. Inspect the quote’s steps and final destination transaction. See Intent types.
Verify its EIP-712 signature against the source chain’s published quoteSigner, then validate the route, recipient, amounts, and expiry. See Quote verification.
For an exact-input quote, destination.amountOut is the expected output and destination.minAmountOut is the stated minimum. Check that the executable route enforces your required output. If a fulfillment transaction cannot meet its encoded conditions, it can revert; that does not immediately execute a source refund. See Request a quote.
Listing a token does not guarantee liquidity for every pair or amount. Check the requested chains, token addresses, amount, and returned error. See Supported chains and tokens.

Deposit addresses

Check the deposit product’s funding threshold and deadline. For Circle Gateway deposits, use the quote and status response to determine whether funding is complete or recovery is required. See Circle Gateway deposits.
No. Publication precedes fulfillment and balance credit. Follow the intent and confirm the destination Gateway balance. See Funding methods.

Sauce

No. Routes supports destination calls directly. Sauce adds programmable logic, such as reading state and selecting an execution branch. See Destination calls and Programmable Transactions.
The documented @eco-incorp/sauce 0.99.4 release requires Node 24 or later for its Node APIs. Browser-compatible entry points are documented separately. See Sauce SDK.
Kitchen-mediated execution includes the configured native-token execution fee and transaction gas. Read the current fee before submitting. See Sauce architecture and deployments.
Review the compiler API and architecture and deployments for the versions you use. Compiler output, engine compatibility, and upgradeability are version-specific.

Next steps

Use Support for unanswered questions or Build with AI agents to connect a coding agent to the docs.