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

# Overview

Venzo Swap is a core component of the Venzo ecosystem, designed to provide users with instant, low-cost asset exchange capabilities. It leverages chain abstraction to eliminate the complexities of bridging, gas tokens, and fragmented liquidity pools that plague the current multi-chain DeFi landscape.

For the average user, swapping assets across different blockchains is one of the most confusing and error-prone experiences in crypto. Venzo Swap solves this by presenting a single, unified interface where users can exchange any supported asset on any supported chain with a single tap. No bridging, no gas token management, no manual route selection.


---

# 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://venzofinance.gitbook.io/venzofinance-docs/venzo-swap/overview.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.
