Skip to main content
The Spot Router is the aggregation and execution layer behind spot trading on Arcus. Through a single integration it evaluates liquidity across the Arcus RFQ network, on-chain AMMs and external venues, selects the best available route for each trade, and settles it on-chain — non-custodially, with no native gas token needed (the gas cost is charged in the trade token).
This page is for integrators. For what spot is — custody, fees, gas, and liquidity sources — see Stock Tokens; for partner economics and onboarding, see Spot integration.

How a trade flows

1

Quote

The integration requests firm quotes (GET /v1/quote) for a given sell token, buy token, size, and taker. The router returns the quotes with a recommended pick and a payload for the user to sign. Each quote itemises its fees. Use GET /v1/price for indicative pricing without a signable payload.
2

Sign

The integration picks one quote (usually recommended) and the user signs that quote’s toSign payload (EIP-712 typed data) from their own wallet. The signature commits to that quote’s venue.
3

Submit

The integration submits the signed payload for that venue (POST /v1/submit). An Arcus quote is a slippage-bounded intent (slippageBps) rather than a fixed maker price, so Arcus re-polls its RFQ makers at execution time and fills with the best firm quotes then. Quotes from other venues execute the payload that venue quoted.
4

Settle

The trade settles atomically on-chain. For token-to-token trades the router submits the transaction, so the user needs no native gas token; the gas cost is charged in the trade token. Track a submitted trade with GET /v1/status.
The venue is fixed when the user signs. For Arcus quotes, maker liquidity is chosen at submission rather than locked in at quote time, so the time a user spends approving does not limit which makers can fill the trade.

Quote options

  • allowWrapped — opt in to wrapped-token settlement of the buy token. Defaults to false, and must match the signed intent.
  • builderFeeBps — a per-request partner fee, repeated on /v1/submit; see Spot integration.
  • chainId — optional sanity check; when present it must match the router’s chain.
The full parameter reference is in each router’s openapi.json.

API surface

Each chain has its own router host: Each router also serves its machine-readable OpenAPI document at /openapi.json.

Integrate

API keys, partner fees, SDKs, and the maker protocol are covered in Spot integration.

Learn more

Spot integration

Partner economics, environments, and integrator FAQ.

Spot RFQ

The request-for-quote model behind the router’s RFQ liquidity.