> For the complete documentation index, see [llms.txt](https://taptools.gitbook.io/taptools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://taptools.gitbook.io/taptools/pro-features/wallet-profiler/overview.md).

# Overview

<figure><img src="/files/3U0ey4AdQgacml1XsHy5" alt=""><figcaption><p>Wallet Profiler Overview</p></figcaption></figure>

Wallet Profiler Overview provides a quick summary of a wallet’s holdings, volume, and overall activity. On the left, the total market value and liquid value are shown; liquid value represents assets that can be instantly converted into ADA (for example, NFTs without active collection offers are not considered liquid). Below that is a breakdown of the wallet’s current holdings, including tokens, NFTs, and LP positions. On the right, activity patterns are displayed, showing every instance the wallet was involved in a transaction. This helps determine whether the wallet is more passive or active. It also highlights the specific days of the week and hours of the day when the wallet is most active.


---

# 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://taptools.gitbook.io/taptools/pro-features/wallet-profiler/overview.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.