Migrating an Odos API integration

Ophis offers a narrow quote-shape compatibility layer, not a drop-in replacement for a router. Check the boundaries before changing a base URL.

Last updated:

Use the compatibility layer only when all of this is true

  • You send one ERC-20 input and request one ERC-20 output.
  • An EOA signs the resulting order with EIP-712 or ethsign.
  • You trade on an enabled Ophis-operated chain.
  • You can settle asynchronously through an intent rather than receive router calldata.
  • You do not require native ETH, zaps, baskets, or the wider Odos endpoint surface.

If every condition holds, review the current production status and field mapping in the complete Odos compatibility reference. The detailed page documents live endpoints, limits, pricing, error classes, and settlement polling.

Use the SDK for broader integrations

Use the partner SDK path when you need a Safe, smart account, vault, hosted chain, or direct control over the signing and orderbook flow. The SDK resolves the correct domain and host across supported chains, including Base, Avalanche, and Ink.

The settlement-model difference

A router API typically returns calldata for an atomic transaction. Ophis returns a bounded, signable order that solvers compete to settle later. There is no transaction object to compose inside another contract call. That is an architectural boundary, not a missing response field.

The trade-off is a gasless user order with a hard signed limit and batch-auction MEV protection. Your integration must follow order status until the order fills, expires, or is cancelled.

Is Ophis a drop-in replacement for the full Odos API?

No. Ophis provides a narrow Odos v3 quote-shape compatibility layer for one ERC-20 input, one ERC-20 output, EOA signing, and Ophis-operated chains. It returns a signable intent rather than executable router calldata.

Can a Safe or smart account use the Odos compatibility layer?

No. The compatibility surface accepts EIP-712 and ethsign from an EOA; it does not expose contract-validated signing schemes. Safe, smart-account, vault, MPC-with-contract-validation, and DAO integrations should use the Ophis SDK path instead.

Does the compatibility API support Base or Avalanche?

No. The compatibility surface is limited to Ophis-operated chains. Integrations that need Base, Avalanche, Ink, Ethereum, Arbitrum, or another CoW-hosted chain should use the Ophis SDK and per-chain orderbook flow.