# Page Not Found

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

## Suggested Pages

You may be looking for one of the following:
- [Addresses & Endpoints](https://fastlane-labs.gitbook.io/polygon-fastlane/searcher-guides/addresses-and-endpoints.md)
- [Design Principles](https://fastlane-labs.gitbook.io/polygon-fastlane/what-is-polygon-fastlane/design-principles.md)
- [Subscribe Events](https://fastlane-labs.gitbook.io/polygon-fastlane/searcher-guides/bundles-backruns/subscribe-events.md)
- [Estimating Solver Gas Charges](https://fastlane-labs.gitbook.io/polygon-fastlane/searcher-guides/searcher-contract-integration/estimating-solver-gas-charges.md)
- [Solver Concepts](https://fastlane-labs.gitbook.io/polygon-fastlane/searcher-guides/searcher-contract-integration/solver-concepts.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://fastlane-labs.gitbook.io/polygon-fastlane/searcher-guides/addresses-and-endpoints.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://fastlane-labs.gitbook.io/polygon-fastlane/sitemap.md

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

### Option 3 — Retrieve the full documentation corpus

Full export: https://fastlane-labs.gitbook.io/polygon-fastlane/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., `/polygon-fastlane/searcher-guides/addresses-and-endpoints.md`).

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