# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Contacting Support](https://ethereum-privacy-machine.gitbook.io/product-docs/community-and-support/contacting-support.md)
- [How to Acquire EPM Tokens](https://ethereum-privacy-machine.gitbook.io/product-docs/getting-started/how-to-acquire-epm-tokens.md)
- [Privacy-Focused Applications](https://ethereum-privacy-machine.gitbook.io/product-docs/use-cases/developers-use-cases/privacy-focused-applications.md)
- [Privacy-Enhanced Smart Contracts](https://ethereum-privacy-machine.gitbook.io/product-docs/use-cases/developers-use-cases/privacy-enhanced-smart-contracts.md)
- [How the Transaction Mixer Works](https://ethereum-privacy-machine.gitbook.io/product-docs/epm-utility/mixer-encrypted-transactions/how-the-transaction-mixer-works.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://ethereum-privacy-machine.gitbook.io/product-docs/community-and-support/contacting-support.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://ethereum-privacy-machine.gitbook.io/product-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://ethereum-privacy-machine.gitbook.io/product-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., `/product-docs/community-and-support/contacting-support.md`).

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