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

# Analytics

### Token Performance

For Users looking invest their tokens, Squirrel Wallet offers built-in data analytics to track token performance. Users are able to seamlessly see how the cryptocurrencies markets are performing and gather data for their investments.

![](/files/AUIv6bejAzeey9nCJ39b)

In this interface users will be able to see everything that's going on with tokens in the market such as:

* Trade Data of specific tokens
* Current Liquidity supply
* Existing Liquidity pool pairs
* Price Changes
* Token Volume&#x20;

### Staking

Squirrel wallet will also track staking progress stats directly in the App. Here users will be able to get a gauged of how well their burying of their NUTS has been going.

Information such as:

* TVL (Total Value Locked)
* APR (Annual Percent Rate) - Broken into different time periods&#x20;
* NUTS Earned -  Broken into different time periods&#x20;

![](/files/r3G0GsjtUVsBdsASJM4g)


---

# 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:

```
GET https://squirrel-wallet.gitbook.io/squirrel/products/squirrel-wallet/analytics.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.

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.
