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

# trade tokens

You can trade any RobinFun token from its token page — on the bonding curve before graduation, and on Uniswap afterward. The experience is the same either way; the app routes your trade automatically.

## Buying

1. Open a token's page.
2. Enter the amount of **ETH** you want to spend.
3. Optionally adjust the **slippage** tolerance.
4. Select **Buy** and confirm in your wallet.

You receive tokens at the current curve (or market) price. A **1% fee** applies — see [Fees](broken://pages/349b82502bf6b60bf1f969e10f862a3091968e68).

## Selling

1. Enter the amount of **tokens** you want to sell.
2. Optionally adjust slippage.
3. Select **Sell** and confirm.

You receive ETH at the current price, minus the 1% fee. During the curve phase you can always sell back — the ETH paid in by buyers backs every position.

## Slippage

Slippage tolerance protects you from price movement between when you submit and when your transaction confirms. If the price moves beyond your tolerance, the transaction reverts instead of filling at a worse price.

| Setting   | When to use it                                          |
| --------- | ------------------------------------------------------- |
| 0.5% – 1% | Quiet tokens, tighter execution.                        |
| 3% – 5%   | Fast-moving tokens with many concurrent buyers.         |
| Custom    | Anything up to 50%. The app warns you at 10% or higher. |

## Curve vs. Uniswap

| Phase             | Where your trade executes                                 |
| ----------------- | --------------------------------------------------------- |
| Before graduation | Against the bonding curve, in ETH.                        |
| After graduation  | On the token's Uniswap V2 pool. The 1% fee still applies. |

{% hint style="info" %}
When a curve is completely full and waiting for [graduation](broken://pages/038ff60edf8d275bc3c88ce6784e9fecfe7bc2de) to finalize, trading pauses briefly until the token is live on Uniswap.
{% endhint %}

## Reading the token page

* **Market cap chart** — candlestick chart of the token's USD market cap, continuous across the curve and Uniswap phases.
* **Progress bar** — how close the token is to graduation.
* **Holders / Trades** — live on-chain activity.
* **Market cap & 24h volume** — headline stats.

{% hint style="warning" %}
Prices on a bonding curve can move sharply. Only trade what you can afford to lose. See the [Disclaimer](broken://pages/bc9d0f00ccf1a3c70dccc076b15af6784a93013d).
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://robinfun.gitbook.io/robinfun-docs/trade-tokens.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.