Pegaroute

We started on the other side of this problem. Building integrations for wallets and apps, we kept wiring the same cross-chain providers over and over, each with its own quirks, each breaking in its own way, and each covering a different slice of chains. The gaps were always the same: Bitcoin, privacy assets, and newer networks like Canton. So we built the layer we wished existed, one API that quotes every provider at once and hands back a signed-ready route, then opened it up to everyone else.

Pegaroute aggregates more Canton liquidity than any other router, across atomic-swap and pooled rails, and connects it to 10,000+ assets on 70+ chains. Because every provider is quoted on every swap, they compete for the order and the user gets the best net price, not the price of whichever venue you happened to integrate. Funds never leave the user’s wallet. Failed venues are skipped automatically. Integrators set their own fee on every route and earn from day one.

Because this is where our community is. The projects we’re closest to, the people we build with, and the problems we care about are on Canton. We believe in what the network is doing with regulated, institutional liquidity, and we want to be the layer that connects it to everything else. That’s not a strategy decision so much as a statement of where we already are.

Canton routing alongside Bitcoin and compliant Monero and Zcash paths, in the same API as the major L1s and L2s. Multiple providers competing on every quote rather than a single venue. Noncustodial end to end. And a partner-fee model that lets any integrator monetise every supported asset from day one.

A single routing API for wallets, DEXs and dapps: parallel quotes across every connected provider, route ranking by net output, ready-to-sign transactions, and full lifecycle tracking via polling, websockets or webhooks. Partner-fee configuration lets integrators set their own bps on routed volume. Coverage spans 10,000+ assets on 70+ chains, with Canton routing, Bitcoin, and compliant Monero and Zcash paths. Delivered as API/SDK, a hosted widget, or link-out referral, depending on how the integrator wants to ship.

Pegaroute sits between the integrator and the liquidity venues. On each request it fans out quotes to every provider that can serve the pair (Squid, THORChain, Maya, OpenOcean, SwapSpace, InstaSwap and others), normalises the responses, and scores them on net output first, then time and slippage. The winning route comes back as an unsigned transaction for the user’s own wallet, so Pegaroute never holds keys or funds. Circuit breakers watch venue health and drop halted or failing routes before they reach the user. Canton routes run through atomic-swap and pooled-liquidity rails with on-ledger settlement, so Canton assets reach the rest of the ecosystem without leaving the network’s compliance model.

Out of stealth October 2026. First set of integrations going live in the coming weeks. Every integrator that connects turns its existing user base into cross-chain volume for Canton, which is the point: more apps routing to Canton means more liquidity reaching the network from the rest of DeFi.

Not applicable. Pegaroute is routing infrastructure; yield, staking and perps routing are on the roadmap.

No airdrop or token. Our launch offer for Canton projects: integrators who go live with Pegaroute now get hands-on integration support from our team and co-marketing across the ecosystems we route. DM us on X or use the access form at pegaroute.com.

Next up: more Canton rails as partners go live, plus a growing provider set competing on every quote. Yield, staking and perps routing follow, so integrators can offer more than swaps through the same API. Longer term, a front end of our own and x402 support.