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

# AnySwap

AnySwap is a non-custodial cross-chain swap and bridge protocol that routes tokens between blockchains in a single flow. Users trade directly from their own wallets; the protocol never takes custody. The primary interface and account overview live in the [AnySwap App](https://anyswap.uk/), while active positions and balances are managed from the [dashboard](https://anyswap.uk//dashboard/). For background on how cross-chain messaging and asset bridging work at the protocol level, Ethereum.org's [bridges documentation](https://ethereum.org/en/developers/docs/bridges/) is a solid primer.

## Core Functions

* **Bridge** — move assets across chains through the [cross-chain bridge](https://anyswap.uk//bridge/), which selects a route and settles on the destination network.
* **Farms** — supplied liquidity can earn yield through the [farms](https://anyswap.uk//farms/), which reward liquidity providers on supported pools.
* **Explorer** — every transfer is verifiable; track status and history via the [on-chain explorer](https://anyswap.uk//explorer/).

## Supported Networks & Assets

AnySwap connects major EVM networks; the current list is maintained on the [supported networks](https://anyswap.uk//network/) page, and asset onboarding is handled through [listing](https://anyswap.uk//listing/). Full protocol specifications, contract references, and integration notes are collected in the [technical documents](https://anyswap.uk//documents/).

## Governance & Project

Protocol parameters and upgrades are managed through [governance](https://anyswap.uk//governance/), where proposals and voting determine changes to supported routes, fees, and incentives. Broader context on the project and its roadmap is available on the [about](https://anyswap.uk//about/) page and the [blog](https://anyswap.uk//blog/).

## Using AnySwap Safely

* Verify the destination network and canonical asset before confirming any bridge or swap.
* Confirm transaction status on the explorer rather than assuming a pending transfer has failed.
* Cross-chain routes settle asynchronously — expect a short delay between source-chain confirmation and destination-chain arrival.

Common questions — fees, timing, and supported wallets — are answered in the [FAQ](https://anyswap.uk//faq/), and live per-bridge volume across the ecosystem can be tracked on [DefiLlama's bridges dashboard](https://defillama.com/bridges). For anything unresolved, the [support](https://anyswap.uk//support/) desk and [contact](https://anyswap.uk//contact/) channels are the fastest path to a human.

## Legal

Use of the protocol is subject to the [terms of service](https://anyswap.uk//terms/) and the [privacy policy](https://anyswap.uk//privacy/).


---

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