> For the complete documentation index, see [llms.txt](https://docs.napier.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.napier.finance/curate/napier-curation/manage-market/claim-fees.md).

# Claim Fees

Curators can claim fees earned from their markets via the Curator Dashboard. 

### Using the Curator App

Follow the steps below to claim fees.

{% stepper %}
{% step %}

### Step 1: Preparation

* Access the **Curator Dashboard**.
* If your account is not verified, complete verification under **Verify Your Account**.
* If you haven’t created a market yet, follow the steps in **Create Market**.
* If you haven’t assigned **Fee Collector**, follow the **Role Allocation** guide to assign the role.
  {% endstep %}

{% step %}

### **Step 2: Claim Curator Fees**

* Click claim fees
* Select one, multiple, or **all** fee items to claim.
* **Review your selections** to ensure accuracy.
* **Click *****Claim selected*** and confirm the transaction in your wallet.

<div align="left" data-with-frame="true"><figure><img src="/files/YIgIb1ns59ymhUWiq3sB" alt="" width="375"><figcaption></figcaption></figure></div>
{% 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 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.napier.finance/curate/napier-curation/manage-market/claim-fees.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.