> For the complete documentation index, see [llms.txt](https://docs.bounce.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bounce.tech/basics/guides/buying.md).

# Buying

To buy a leveraged token, go to [bounce.tech/trade](https://bounce.tech/trade). This opens the Trade page, where you pick an asset, Direction, Leverage, and a USDC Buy amount, then click Place order.

On the Bounce UI, the size you enter is denominated in USDC, not in leveraged token units. **Trade details** converts that USDC into the token you will receive (for example `HYPE5L`).

#### 1. Log in

Click **Log in** in the header or on the buy panel. Users can log in with email, Google, or a crypto wallet such as Rabby or MetaMask. After logging in, deposit USDC to start trading.

#### **2. Select the asset you want to trade**

Click the market selector above the chart (for example HYPE-USDC). Search with ⌘K, or filter by Stocks, Commodities, Crypto, and ETFs.

<figure><img src="https://3196478238-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbP0mVSZkn1FNFNjoaAxL%2Fuploads%2F4d9uum2kvSvS8P40zGqH%2FScreenshot%202026-09-10%20at%201.12.29%E2%80%AFPM.png?alt=media&amp;token=b247fc5a-d348-4ba4-ae90-28a5772b2383" alt=""><figcaption><p>You can also switch the chart between <strong>Underlying Chart</strong> (the Hyperliquid perp) and <strong>Leveraged Token Chart</strong>.</p></figcaption></figure>

#### 3. Select Direction, Leverage, and Buy amount

In the right-hand panel:

1. Set Direction to Long or Short.
2. Set Leverage (2x / 3x / 5x; some shorts also offer 1x).
3. Enter USDC buy amount.

After entering an amount, expand **Trade details** to review:

* You receive: Estimated leveraged tokens received&#x20;
* Min. received: The slippage protected minimum you will receive
* Position: Asset, leverage, direction, and token symbol
* Fees: 0% for buys, 0.3% for sells

{% hint style="info" %}
Trades on Bounce have a minimum order size of $15 USDC. If you are below the minimum size threshold, a panel will open showing insufficient amounts. If this happens, increase your order size to > $15
{% endhint %}

#### 4. Place order&#x20;

For users that log in via Google or email, no further steps are required after clicking Place order. For crypto wallet users, orders must be signed by your wallet as standard.&#x20;

**Crypto wallet users only**\
If it's your first time placing an order, you will be prompted to sign two transactions. One for approval and one for executing the order. Approval transactions only occur the first time you buy a leveraged token, future orders will only require one transaction.&#x20;

#### 5. View position

After placing an order, view your position on the [Portfolio page](https://bounce.tech/portfolio) or directly on the trade page via the Positions table below the chart.&#x20;


---

# 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://docs.bounce.tech/basics/guides/buying.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.
