> For the complete documentation index, see [llms.txt](https://roostlaunch.gitbook.io/roost-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://roostlaunch.gitbook.io/roost-docs/use-roost/payment-tokens.md).

# Payment tokens

Every market uses a payment token. Buyers spend it to buy the launched token, and sellers receive it when they sell. The creator selects the payment token at launch.

***

#### ETH

The default pairing. The interface shows ETH to users and wraps it as WETH wherever the pool requires an ERC-20 asset.

***

#### Robinhood Stock Tokens

Robinhood Stock Tokens are ERC-20 tokens on Robinhood Chain that carry economic exposure to underlying US stocks and ETFs. A creator can select a supported Stock Token instead of ETH. A stock-paired market can look like MEME / SPCX: buyers spend SPCX to buy MEME, and sellers receive SPCX when they sell.

***

#### Supported payment tokens

Roost supports a curated set of payment tokens rather than the full Robinhood Chain asset registry. The set at launch is:

<table><thead><tr><th width="105.9609375" valign="top">Symbol</th><th width="395.45703125" valign="top">Asset</th><th valign="top">Type</th></tr></thead><tbody><tr><td valign="top">ETH</td><td valign="top">Ether (wrapped to WETH in pools)</td><td valign="top">Native asset</td></tr><tr><td valign="top">NVDA</td><td valign="top">NVIDIA Corporation</td><td valign="top">Stock Token</td></tr><tr><td valign="top">SPCX</td><td valign="top">SpaceX</td><td valign="top">Stock Token</td></tr><tr><td valign="top">GOOGL</td><td valign="top">Alphabet Inc. Class A</td><td valign="top">Stock Token</td></tr><tr><td valign="top">GME</td><td valign="top">GameStop Corp.</td><td valign="top">Stock Token</td></tr><tr><td valign="top">AAPL</td><td valign="top">Apple Inc.</td><td valign="top">Stock Token</td></tr><tr><td valign="top">SPY</td><td valign="top">SPDR S&#x26;P 500 ETF Trust</td><td valign="top">Tokenized ETF</td></tr><tr><td valign="top">SNDK</td><td valign="top">SanDisk Corporation</td><td valign="top">Stock Token</td></tr><tr><td valign="top">AMZN</td><td valign="top">Amazon.com, Inc.</td><td valign="top">Stock Token</td></tr><tr><td valign="top">MSFT</td><td valign="top">Microsoft Corporation</td><td valign="top">Stock Token</td></tr><tr><td valign="top">META</td><td valign="top">Meta Platforms, Inc.</td><td valign="top">Stock Token</td></tr><tr><td valign="top">MU</td><td valign="top">Micron Technology, Inc.</td><td valign="top">Stock Token</td></tr><tr><td valign="top">PLTR</td><td valign="top">Palantir Technologies Inc.</td><td valign="top">Stock Token</td></tr><tr><td valign="top">HOOD</td><td valign="top">Robinhood Markets, Inc. (Ondo tokenized)</td><td valign="top">Tokenized stock</td></tr><tr><td valign="top">USDG</td><td valign="top">Global Dollar</td><td valign="top">Stablecoin</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://roostlaunch.gitbook.io/roost-docs/use-roost/payment-tokens.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
