Skip to main content
The Spot Router is built to be integrated. Wallets and applications can offer Stock Token trading through a single integration while Arcus handles pricing, routing, execution, and settlement; professional market makers can connect to provide RFQ liquidity. This page covers what integrating looks like and answers common questions — for the API flow and endpoints, see Spot Router.
Integrating requires an API key issued by Arcus, so getting in touch is the first step. To request access or discuss an integration, contact the Arcus team.

What you can build

Wallets & applications

Embed Stock Token trading directly in your own interface. You keep the frontend and the user relationship; Arcus provides pricing, routing, execution, and settlement behind it.

RFQ market makers

Connect to the RFQ network to quote against taker flow from Arcus and integrated partners. You choose which tokens to quote.

What a single integration provides

Rather than building and maintaining a connection to each liquidity source, a partner integrates once and gets:
  • Every liquidity source the router uses — the RFQ network, on-chain AMMs, and external venues, evaluated together for best execution (see how Arcus sources liquidity).
  • The Stock Token catalogue — without sourcing and integrating market makers for each name. The live list is served by the router (GET /v1/tokens).
  • Self-custodial trading with no native gas token needed — the gas cost is charged in the trade token (see Stock Tokens).

Builder codes and economics

Each integration is issued a dedicated API key, and volume routed through the key is attributed to the partner. Partners earn revenue by setting a builder fee per request: pass builderFeeBps on GET /v1/quote (with the API key) and repeat the same value in the POST /v1/submit body. The value must not exceed the maximum configured for the key; omitting it, or passing 0, collects no builder fee. The fee is paid to the recipient configured for the key. The key’s maximum and fee recipient are set up with the Arcus team during onboarding.

Environments

Each chain has its own router host. chainId on a request is an optional sanity check and must match the router’s chain.

FAQ

Reach out to the Arcus team. Integrations require an API key (which carries your builder-fee maximum and recipient), so getting in touch is the first step; you’ll receive SDKs, a testnet sandbox, and integration support.
Tokenized stocks, plus other supported markets. The canonical, live list is served by each router at GET /v1/tokens, so there is no static list to maintain.
For token-to-token trades, no — the router submits the transaction and the gas cost is charged in the trade token. Paying with the chain’s native asset is the exception, where the user broadcasts and pays gas.
Yes. Trading is fully self-custodial — users hold their Stock Tokens and authorize every trade with their own signature. See self-custody.
The router evaluates available liquidity across sources and executes each trade against the best available route, chosen at submission time. See Spot Router and Spot RFQ.
Through builder codes: volume routed through your API key is attributed to you, and you set builderFeeBps per request up to your key’s maximum. See Builder codes and economics.
Yes — Robinhood Chain testnet (chain ID 46630, router https://router.spot.testnet.arcus.xyz) for end-to-end validation before going live.
Reach out to the Arcus team. Makers run a maker server that receives RFQ requests for the tokens they choose to quote, and respond with firm, signed quotes. See Spot RFQ for the model.

Learn more

Spot Router

The quote-sign-submit flow, router hosts, and endpoints.

Spot RFQ

The request-for-quote model behind RFQ liquidity.