> For the complete documentation index, see [llms.txt](https://docs.speedboat.studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.speedboat.studio/speedboat-v1/tutorial/claiming-your-sales-proceeds.md).
# Claiming Your Sales Proceeds
{% hint style="info" %}
**We currently do not have a UI to claim your project sales proceeds on our platform. However you can do it manually by visiting** [**https://polygonscan.com/**](https://polygonscan.com/)
{% endhint %}
* Go to your project's sales page
* Copy the contract address (highlighted in blue in the image below)
* Go to
* Paste the contract address
* Click on the `Contract` tab
* Click on `Write Contract` then click on `Connect to Web3`
* Connect to your MetaMask wallet
* Scroll down to `8. withdraw` and click `Write`
* `Confirm` your transaction on MetaMask
* The Proceeds from your NFT sales will now be sent to your wallet
{% hint style="info" %}
As a platform fee, Speedboat will receive 2% of the sales proceeds
{% endhint %}
---
# 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.speedboat.studio/speedboat-v1/tutorial/claiming-your-sales-proceeds.md?ask=&goal=
```
`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.