> 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/resources/glossary.md).

# Glossary

## Bankroll

Your available POLL point balance in paper mode.

## Claim

The action that credits your paper wallet after a resolved winning position.

## Creator bonus

The publish reward paid when a user launches a paper market. Default: **100 POLL**.

## Creator fee pool

The portion of paper trading fees reserved for the creator and paid out when the market resolves.

## Daily refill

A once-per-day top-up that restores low-balance accounts from the refill floor to the refill target.

## LS-LSMR

Liquidity-Sensitive Logarithmic Market Scoring Rule. The pricing engine that updates probabilities after each trade.

## POLL

The points label used in paper mode.

## Price impact

How much a trade moves the market price.

## Resolution criteria

The exact written rules that determine how a market should resolve.

## Share

A unit of exposure to an outcome. Winning shares settle at **1 POLL point**.


---

# 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/resources/glossary.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.