# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Exchanges,Wallets,On-Ramps and Defi Tools Supporting METABENZ](https://metabenz.gitbook.io/metabenz/general/exchanges-wallets-on-ramps-and-defi-tools-supporting-mfev.md)
- [Stake, Delegate and Withdraw](https://metabenz.gitbook.io/metabenz/general-1/metabenz-consensus/stake-delegate-and-withdraw.md)
- [METABENZ Blockchain Token](https://metabenz.gitbook.io/metabenz/general/metabenz-token.md)
- [Deploying smart contract on METABENZnet](https://metabenz.gitbook.io/metabenz/consumer-tutorials/deploying-smart-contract-on-fusenet.md)
- [Resources & Tools](https://metabenz.gitbook.io/metabenz/general-1/resources-and-tools.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://metabenz.gitbook.io/metabenz/general/exchanges-wallets-on-ramps-and-defi-tools-supporting-mfev.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://metabenz.gitbook.io/metabenz/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://metabenz.gitbook.io/metabenz/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., `/metabenz/general/exchanges-wallets-on-ramps-and-defi-tools-supporting-mfev.md`).

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