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 on-chain AMMs and the Arcus RFQ network, selects the best available route for each trade, and settles it on-chain — non-custodially and, in most cases, gasless. Wallets and applications integrate once instead of building and maintaining a connection to each liquidity source.
This page is for integrators. For what Stock Tokens are and how they settle to your wallet, see Stock Tokens; for the request-for-quote model, see Spot RFQ.

​
Liquidity sources

The router aggregates liquidity from several sources and executes each trade against the source — or, for on-chain pools, the combination of pools — that offers the best price: For each trade the router selects the best available execution across these sources, and may source on-chain AMM liquidity from more than one pool.

​
How a trade flows

1

Quote

The integration requests a quote (GET /v1/quote) for a given sell token, buy token, and size. The router returns the best available route and a payload for the user to sign. Use GET /v1/price for indicative pricing without a signable payload.
2

Sign

The user signs the returned intent (EIP-712 typed data) from their own wallet. Signing commits to a slippage-bounded outcome, not to a specific route.
3

Submit

The integration submits the signed payload (POST /v1/submit). The router evaluates liquidity at execution time and picks the best route then — so the time a user spends approving does not constrain which sources can fill the trade.
4

Settle

The trade settles atomically on-chain. Settlement is gasless for token-to-token trades — the router submits the transaction — so the user does not need to hold a gas token. Track a submitted trade with GET /v1/status.
Because the route is chosen at submission rather than locked in at quote time, the router can use whatever liquidity is best when the trade actually executes.

​
Gasless and self-custodial

Users remain self-custodial throughout: Stock Tokens stay in the user’s wallet and every trade is authorized by the user’s own signature (see self-custody). For most trades the router submits the settlement transaction on the user’s behalf, so no separate gas token is required. Buying with the chain’s native asset is the exception — there the user broadcasts the transaction and pays gas.

​
API surface

The router is served at https://router.spot.arcus.xyz. Supported chains: Robinhood Chain mainnet (chainId 4663) and testnet (chainId 46630).

​
Partner economics

Each integration is issued a dedicated API key. Volume routed through the key is attributed to that partner, and a partner (builder) fee can be configured against the key. Fee configuration and attribution are set up with the Arcus team during integration onboarding rather than passed per trade.

​
Integrate

Stock Token trading can be embedded directly in a wallet or application: the partner keeps its own interface and user relationship while the router handles pricing, routing, execution, and settlement. RFQ market makers can connect to the network to quote against incoming taker flow. SDKs, reference implementations, and the maker protocol specification are provided during onboarding. To start an integration or join the RFQ network, contact the Arcus team.

​
Learn more

Stock Tokens

What Stock Tokens are and how they settle to your wallet.

Spot RFQ

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