> For the complete documentation index, see [llms.txt](https://docs.bloombot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloombot.app/solana/solana-bot/pnl-calendar.md).

# PnL Calendar

{% hint style="info" %}
The PnL Calendar is the easiest way to keep track of your trading performance inside Bloom.

It gives you a day-by-day view of your results for each month, helps you analyze your performance, and allows you to instantly generate a recap image that can be shared on Twitter \[X] in one tap.
{% endhint %}

{% embed url="<https://youtu.be/ciA7GzI07a4>" %}

### How to Use the PnL Calendar

{% stepper %}
{% step %}
**Choose your chain**

Select the blockchain (ETH, BSC, Base, etc.) for which you want to view your PnL calendar.
{% endstep %}

{% step %}
**Select the month**

Pick the month you want to generate the PnL data for.
{% endstep %}

{% step %}
**Select the week**

Narrow down your view by choosing a specific week within that month.
{% endstep %}

{% step %}
**Choose the format**

Decide if you’d like to see your PnL results in the blockchain’s native currency or converted into USD.
{% endstep %}

{% step %}
**Generate your recap**

Tap Generate Recap to create a visual monthly PnL recap image.
{% endstep %}

{% step %}
**Share your performance**

Tap Share to instantly post your PnL recap on Twitter \[X].
{% endstep %}
{% endstepper %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bloombot.app/solana/solana-bot/pnl-calendar.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.