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

# Trading

## Making a trade

1. Connect your wallet.
2. Pick a token from **the board**, or paste any **contract address** into search — if it's on the chain, it's tradeable.
3. Enter an amount and swap. Your order routes through the 0x aggregator for the best available price.
4. Review and sign in your wallet. Fills confirm in under a second.

## Fees

A flat **0.25%** on every swap. No tiers, no hidden spreads.

## Reading the market

Every token opens in the terminal with **live candles, market cap, and a real-time trade tape** — straight from the chain, not a delayed third-party feed.

## Risk flags

Tokens carry heuristic **risk flags** to help you spot rug patterns before you trade.

> Risk flags are signals, not guarantees. Always do your own research.


---

# 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://hoodswaps.gitbook.io/hoodswaps-docs/trading.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.