Routing is the product
If your company's value is execution quality, it has to be yours. Use us as a benchmark instead. The quote endpoint returns every losing route, so you can measure your own book against it.
Build it, or integrate it
Routing is not hard the way people expect. It is hard the way that never ends. The first integration takes a sprint. The twentieth is still there next quarter, breaking.
The work, either way
The same list whichever path you take. The only difference is who carries it.
| What it involves | If you build it | If you integrate |
|---|---|---|
| Venue integrations | 17 venues, each with its own auth, quote shape, amount encoding, execution model and error vocabulary. | One endpoint. We flatten the differences before you see them. |
| Quote normalisation | Making a firm RFQ price, an intent auction and an AMM route comparable enough to rank, after gas, in the output asset. | Ranking is the product. You get the winner and every route that lost. |
| Bitcoin | UTXO selection, PSBT construction, HTLC or threshold-signature settlement, refund binding. A different signing model from every EVM path you have. | Chain ID -1, token "native". A helper builds the signable transaction. |
| Execution models | Sign-and-broadcast, off-chain typed-data signing with solver relay, and send-to-address deposits. Three code paths, not one. | One response field tells you which of the three you got. |
| Failure handling | Stale quotes, partial fills, venue outages, refunds that vary per venue, and a status model that differs everywhere. | One normalised status endpoint, webhooks, and machine-readable error codes. |
| Ongoing maintenance | Venues change APIs, deprecate endpoints, add chains and go down. This never becomes finished work. | Our on-call, not yours. Venue health is published so you can watch it anyway. |
Ranking is the part nobody budgets for
Getting a quote out of six venues takes about a week per venue, in our experience. Deciding which one is actually better is the hard part. You have to compare net of gas, in the output asset, a firm price against one exposed to slippage, and twenty minutes for slightly more against forty seconds for slightly less.
Get it wrong and you have built something that looks like an aggregator and quietly picks the worse trade. That is worse than not aggregating, because now you own the outcome.
When you should build it yourself
Genuinely, sometimes. This page would not be worth reading if it pretended otherwise.
One corridor
If you need exactly one pair on one chain forever, a direct venue integration is less code than any abstraction over it.
Hard custody rules
If compliance requires every counterparty to be contracted directly, an orchestration layer does not remove that requirement.
You already did
If the integrations exist and work, replacing them buys nothing. The only question is whether the next five are worth building too.
What integrating costs
Nothing to start and nothing monthly. No key to request, no contract to sign, and no sales call between you and a working quote. The endpoint is anonymous and CORS-open, so you can judge it before deciding anything.
If you want swaps to be revenue rather than a feature, set your own fee and we pay it out to you. Retail stays 0 bps either way.