> For the complete documentation index, see [llms.txt](https://docs.sol-incinerator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sol-incinerator.com/tool-guide/incinerator/pro-mode.md).

# Pro Mode

Answers to common questions about using Pro Mode.

<div align="left"><figure><img src="https://1873951249-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA5iitZPaneFn10oUprDy%2Fuploads%2FSEolXw6IEmky7RoeIhYK%2Fpromode.png?alt=media&#x26;token=f0a0ed7d-fe60-4207-9c68-15dead74166d" alt="" width="375"><figcaption></figcaption></figure></div>

## Pro Mode FAQ

***

<details>

<summary>What is Pro Mode?</summary>

Pro Mode is the full, standard cleanup experience—letting you intentionally clean your wallet beyond basic rent reclaim across all standard asset types (OG v2)

Enabling Pro Mode gives you access to:

* The **Reclaim** tab for pump.fun rewards, rent refunds, vacant accounts, and unused Serum accounts. Reclaim does not burn.
* The **Tokens Tab** for burning standard SPL tokens
* The **NFTs Tab** for burning NFTs
* The **cNFTs Tab** for burning compressed NFTs
* The **Domains Tab** for burning domains

Dev mode, from the footer, adds the LP and Unknown tabs.

{% hint style="warning" %}
Understand what you’re burning and always double-check the queue before confirming.
{% endhint %}

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

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

```
GET https://docs.sol-incinerator.com/tool-guide/incinerator/pro-mode.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.
