# Page Not Found

The URL `files/ipV4VSvUXQiVG6cnJAdz` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [IMulticall](https://bonsaiswap.gitbook.io/bonsaiswap-docs/developers/technical-reference/periphery/interfaces/imulticall.md)
- [V3Migrator](https://bonsaiswap.gitbook.io/bonsaiswap-docs/developers/technical-reference/periphery/v3migrator.md)
- [Swapping Tokens](https://bonsaiswap.gitbook.io/bonsaiswap-docs/products/exchange/swapping-tokens.md)
- [IPoolInitializer](https://bonsaiswap.gitbook.io/bonsaiswap-docs/developers/technical-reference/periphery/interfaces/ipoolinitializer.md)
- [Interfaces](https://bonsaiswap.gitbook.io/bonsaiswap-docs/developers/technical-reference/core/interfaces.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://bonsaiswap.gitbook.io/bonsaiswap-docs/developers/technical-reference/periphery/interfaces/imulticall.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://bonsaiswap.gitbook.io/bonsaiswap-docs/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://bonsaiswap.gitbook.io/bonsaiswap-docs/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/bonsaiswap-docs/developers/technical-reference/periphery/interfaces/imulticall.md`).

You may also use `Accept: text/markdown` header for content negotiation.