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

# Welcome to FlowRouter

Swap on Robinhood Chain. Understand your route, review your transaction, and build with FlowRouter.

FlowRouter finds routes for token swaps on **Robinhood Chain**. Choose what to sell and buy, compare the quoted output and network fee, and approve the transaction in your wallet.

A route can use one pool, several hops, or split liquidity across venues. FlowRouter brings the quote, route preview, and transaction preparation into one interface.

[**Open the app**](https://flowrouter.xyz/swap/robinhood) · [**Follow FlowRouter on X**](https://x.com/flowrouter_xyz)

## Use FlowRouter

| Start here                                                                | What you will learn                                                |
| ------------------------------------------------------------------------- | ------------------------------------------------------------------ |
| [Your first swap](/flowrouter-docs/use-flowrouter/first-swap.md)          | Connect, choose a pair, review a quote, and swap.                  |
| [Wallets and network](/flowrouter-docs/use-flowrouter/wallets.md)         | Connect a wallet and use ETH on Robinhood Chain.                   |
| [Read a quote](/flowrouter-docs/use-flowrouter/quotes-and-routes.md)      | Understand output, minimum received, route details, and freshness. |
| [Slippage and fees](/flowrouter-docs/use-flowrouter/slippage-and-fees.md) | Understand execution costs and the router's surplus policy.        |
| [Troubleshooting](/flowrouter-docs/use-flowrouter/troubleshooting.md)     | Resolve missing routes, approval issues, and pending transactions. |

## Build with FlowRouter

| Start here                                                                    | What you will learn                                              |
| ----------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| [Integration overview](/flowrouter-docs/build-with-flowrouter/overview.md)    | Choose an interface and understand the integration lifecycle.    |
| [Swap API v1](/flowrouter-docs/build-with-flowrouter/swap-api.md)             | Get prices and ready-to-send swap transactions from your server. |
| [Errors and retries](/flowrouter-docs/build-with-flowrouter/errors.md)        | Handle Swap API errors, request limits, and retries.             |
| [Network and contracts](/flowrouter-docs/reference/networks-and-contracts.md) | Find chain details, deployed addresses, and the swap interface.  |

## What is available?

The documented app targets Robinhood Chain mainnet, chain ID **4663**. Route availability depends on the token pair, amount, liquidity, and current service state. A token appearing in the picker does not guarantee an executable route.

Quoting and transaction execution have separate availability checks. If the app shows that swaps are unavailable, wait for execution to become available before attempting a swap. Developers can check [`GET /v1/health`](/flowrouter-docs/build-with-flowrouter/swap-api.md#health) before they request a price or quote.


---

# 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://flowrouter.gitbook.io/flowrouter-docs/readme.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.