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

# Screenshots index

Images used in these docs (under `docs/gitbook/assets/`).

| File                  | Used in                                                      | Coverage                                                                               |
| --------------------- | ------------------------------------------------------------ | -------------------------------------------------------------------------------------- |
| `logo.svg`            | GitBook site header / favicon (Customization), not page body | Lightning brand mark (same path as VoltArbLogo)                                        |
| `logo.png`            | Favicon-size raster of the bolt (optional)                   | White bolt on blue                                                                     |
| `brand-header.png`    | Archived lockup (bolt + VOLTARB + tagline)                   | Full banner; unused in pages                                                           |
| `hero-tagline.png`    | Archived tagline hero                                        | Unused — do not embed on Introduction                                                  |
| `scanner-table.png`   | Getting started, Ecosystem, Web Terminal (EN + RU)           | Live arb table                                                                         |
| `tracker-cex-cex.png` | Opportunity Tracker (EN + RU)                                | **CEX–CEX** — dual books (Aster Futures → Gate Futures, ARX/USDT)                      |
| `tracker-cex-dex.png` | Opportunity Tracker (EN + RU)                                | **CEX–DEX** — CEX book + DEX Size/Impact/Avg liquidity (Aster → PancakeSwap, AKE/USDT) |
| `tracker-bsb.png`     | *(legacy — not linked)*                                      | Old generic Tracker shot; superseded by the two labeled files above                    |
| `hub-menu.png`        | Telegram hub, Pro (EN + RU)                                  | Hub bot menu                                                                           |
| `bot-filters.png`     | Personal bot filters (EN + RU)                               | Alert floors                                                                           |
| `miniap-routes.png`   | Mini App                                                     | Routes / Demo                                                                          |

> Do **not** swap CEX–CEX / CEX–DEX shots or captions. Site `/docs` hub (DocsPage) should not re-embed these screenshots.

## Nice-to-have next shots

1. **Filters panel** on web (lifetime presets 45s / 2m / 5m)
2. **Fair Price** tab
3. **Funding** combos table
4. **Checkout** USDT BSC
5. **Account + VKEY** paste / Connect Telegram
6. **Pro paywall** on Tracker (3/day Free)
7. Mini App **Live** (API keys screen) — redact secrets

No invented filenames in chapters — only the assets above until new shots land.


---

# 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://voltarb.gitbook.io/voltarb-docs/english/screenshots.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.