> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcus.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Spot integration

> What it takes to integrate the Arcus Spot Router — embedding Stock Token trading in a wallet or app, joining the RFQ maker network, builder-code economics, and answers to common integrator questions.

**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 how routing works under the hood, see [Spot Router](/concepts/spot-router).

<Note>
  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](mailto:vip@arcus.xyz).
</Note>

## What you can build

<CardGroup cols={2}>
  <Card title="Wallets & applications" icon="wallet">
    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.
  </Card>

  <Card title="RFQ market makers" icon="tower-broadcast">
    Connect to the RFQ network to quote against taker flow from Arcus and integrated partners. You choose which tokens to quote.
  </Card>
</CardGroup>

## What a single integration provides

Rather than building and maintaining a connection to each liquidity source, a partner integrates once and gets access to:

* **The Arcus RFQ network** — firm, signed quotes from professional makers, including liquidity for long-tail names that lack deep on-chain pools.
* **On-chain AMM liquidity** and **external liquidity venues**, evaluated together for best execution.
* **The full Stock Token universe** — hundreds of tokenized equities, without sourcing and integrating market makers for each one. The live list is served by the router (`GET /v1/tokens`).
* **Gasless, self-custodial trading** — users trade from their own wallet without needing a separate gas token (native-asset purchases excepted).

## Builder codes and economics

Each integration is issued a dedicated API key. Volume routed through the key is attributed to the partner, and a partner (builder) fee can be configured against it — so partners can earn revenue from trading activity within their own product. Fees and attribution are set up with the Arcus team during onboarding.

## Environments

| Network | Chain ID | Use |
| - | - | - |
| Robinhood Chain mainnet | `4663` | Production trading. |
| Robinhood Chain testnet | `46630` | End-to-end integration testing in a sandbox. |

## FAQ

<AccordionGroup>
  <Accordion title="How do I get started?">
    [Reach out to the Arcus team](mailto:vip@arcus.xyz). Integrations require an API key (which also carries your builder-code configuration), so getting in touch is the first step; you'll receive SDKs, a testnet sandbox, and integration support.
  </Accordion>

  <Accordion title="What assets can my users trade?">
    Hundreds of tokenized stocks, plus other supported markets. The canonical, live list is served by the router at `GET /v1/tokens` (filterable by chain), so there is no static list to maintain.
  </Accordion>

  <Accordion title="Do my users need to hold a gas token?">
    For most trades, no — settlement is gasless and the router submits the transaction. Buying with the chain's native asset is the exception, where the user broadcasts and pays gas.
  </Accordion>

  <Accordion title="Do users keep custody of their assets?">
    Yes. Trading is fully self-custodial — users hold their Stock Tokens and authorize every trade with their own signature. See [self-custody](/concepts/spot-overview#self-custody).
  </Accordion>

  <Accordion title="How is pricing determined?">
    The router evaluates available liquidity across sources and executes each trade against the best available route, chosen at submission time. See [Spot Router](/concepts/spot-router) and [Spot RFQ](/concepts/spot-rfq).
  </Accordion>

  <Accordion title="How do I earn revenue from my integration?">
    Through builder codes: volume routed through your API key is attributed to you, and a partner fee is configured against the key. See [Builder codes and economics](#builder-codes-and-economics).
  </Accordion>

  <Accordion title="Is there a sandbox for testing?">
    Yes — Robinhood Chain testnet (chain ID `46630`) for end-to-end validation before going live.
  </Accordion>

  <Accordion title="How do RFQ market makers join?">
    [Reach out to the Arcus team](mailto:vip@arcus.xyz). 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](/concepts/spot-rfq) for the model.
  </Accordion>
</AccordionGroup>

## Learn more

<CardGroup cols={2}>
  <Card title="Spot Router" icon="route" href="/concepts/spot-router">
    How the router aggregates liquidity and settles each trade.
  </Card>

  <Card title="Spot RFQ" icon="arrow-right-arrow-left" href="/concepts/spot-rfq">
    The request-for-quote model behind RFQ liquidity.
  </Card>
</CardGroup>