Concepts

The route pages are the wire contract: request fields, response shapes, error codes. The pages here are the explanation — why a field behaves the way it does, how several routes fit into one flow, what to do when something goes wrong. The conventions, flows, errors and limits pages and the route pages keep their spec tables and link here.

Page	The question it answers	Spec tables it relies on
Step execution	What does a winning quote hand me, and what do I do with it?	Get quote — Response, Submit order (openFor), Create order
Trade types	Exact input or exact output, firm or auctioned — what changes?	Get quote — Request body, Flows — Auctions
Input validation	What does the hub check, and what can I check first?	Conventions, Get quote — Request
Handling errors	How do I read an error body, and when is it safe to retry?	Error reference, Conventions — The response envelope
Handling rate limits	What’s the budget, and how do I stay under it?	Limits
Execution errors	The order didn’t fill — what does the hub actually know?	Get upstream status — Response, List orders — Response
Refunds	When and how do I get the deposit back?	Get on-chain fill, Get escrow order
Order lifecycle	Which id, and which of the three status routes, do I poll?	Get upstream status, Get hub status

Fees

The hub has no fee concept — it never takes a cut. The one fee on the wire is a solver’s own fee inside a solver-swap winner’s disclosure.signablePayload — part of that solver’s terms, and such a winner is not completable (Step execution). What an order costs the user is entirely inside the quote:

amountIn — what the winner charges, in base units (on the token-in lane the escrow’s wrapped native, so read swapInput.amountMax there) (Get quote — Response, Get quote).
swapInput.amountMax and slippageBps, on the token-in lane only — the ceiling the wallet is asked to approve and the tolerance that produced it (Get quote — Request body, Get quote; Trade types — slippage on the token-in lane).
Gas, per lane — who pays it and when is Step execution — the lanes.

These already read as concept pages and are not duplicated here:

Authentication — the secret key and the project id, origin lists, and keeping your users apart
Quickstart — five calls and one signature
Troubleshooting — symptom → cause → fix, by phase

Get started

Core concepts

Resources

API reference

SDK

SDK reference

Fees

​Fees

​Related pages

Fees

Related pages