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

# FAQ

<details>

<summary>What is the difference between Chat, Monitor, and Recon?</summary>

**Chat** is the natural language workspace for investigating digital asset markets.

**Monitor** is the tracking workspace for keeping useful visualizations refreshed over time.

**Recon** is the client intelligence workspace for fintechs.

</details>

<details>

<summary>Can I create my own monitors?</summary>

**Pro and Enterprise users can create Custom Monitors.**

Free users can only browse Featured Monitors.

</details>

<details>

<summary>Who can access Recon?</summary>

**Recon is available on Enterprise plans only.**

</details>

<details>

<summary>Does Mavrik support MCP connectors?</summary>

**Yes. Mavrik supports MCP connectors for Enterprise customers only.**

</details>

<details>

<summary>What coverage (chains/protocols/tokens) does Mavrik have?</summary>

**Mavrik supports onchain activity across major EVM chains, including Ethereum, Base, Arbitrum, and BNB Chain, as well as Solana.**

Coverage includes most major stablecoins such as USDC and USDT, native tokens, swaps, liquidity, lending, token transfers, and wallet-level behavior.

You can also ask Mavrik directly:

“What can I ask you about?”\
“What coverage do you have?”

Mavrik’s coverage is expanding over time. If there is a specific chain, protocol, asset, or use case you are interested in, [contact us](https://www.validationcloud.io/contact) and we’ll be happy to support.

</details>

<details>

<summary>How should I prompt Mavrik for best results?</summary>

**Mavrik works best when your question is specific.**

Try to include:

* The asset, chain, protocol, or wallet address you want to investigate.
* The metric you care about, such as volume, transfer count, transactions, TVL, number of unique wallets, or wallet balance.
* A time range, such as “in the last 7 days” or “over the past month.” We recommend starting with a short time range, then expanding once you get a useful result.

For example:

“How much ETH on Ethereum has \[wallet address 1] transferred to \[wallet address 2] in the last 7 days?”

</details>

<details>

<summary>Mavrik gave me an error, what do I do?</summary>

**First, retry the prompt.**

If you still cannot get an answer, try rephrasing your question with a clearer metric, asset, chain, wallet address, or time range. Please note, if your question involves a chain, protocol, or asset that is not yet supported, Mavrik will let you know.

You can also send feedback by clicking Help in the left-hand navigation and sending us a message.

</details>


---

# 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://docs.validationcloud.io/mavrik/mavrik/faq.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.