Skip to main content
SaucerSwap exposes three integration surfaces. Most integrations use more than one: read market data from an API, then quote and execute on-chain or through the order book.
SaucerSwap protocol architecture: the V1 AMM, V2 concentrated liquidity, and V3 order book side by side beneath the app's routing layer

The three protocol versions behind the integration surfaces.

The three surfaces

Which surface for which job

V2 is recommended for new AMM integrations; V1 remains live but is legacy. The V3 order book is a separate matching system with its own API and concepts page.

Test before mainnet

Every surface has a testnet counterpart: Create a Hedera testnet account and fund it with test HBAR through the Hedera developer portal. Use a dedicated integration account for bots — never a primary wallet key.

Next steps

Quickstart

Make your first API calls in under five minutes.

Contract deployments

Canonical contract and token IDs with HashScan links.

API reference

Both APIs, authentication models, and every endpoint.

Build with AI

llms.txt, the docs MCP server, and an agent rules file.