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

# Claiming Winnings

When a paper market resolves, winning shares become claimable.

## What a claim does

A claim credits your paper wallet with:

* **1 POLL point per winning share**

Losing shares settle to zero.

## Who can claim

Any user who holds winning shares on a resolved paper market.

## Creator fee note

If you created the market, the paper backend also pays out the accumulated creator fee pool at resolution.

That creator fee payout is separate from a normal trader claim.

## Common reasons a claim is unavailable

* the market is not resolved yet
* you do not hold winning shares
* you already claimed

## Important difference from the old product

Paper claims do **not** send USDC to a wallet.

They update your **POLL point balance** in the paper wallet.


---

# 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://polypoll.gitbook.io/polypoll-docs/user-guide/claiming.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.