> For the complete documentation index, see [llms.txt](https://www.size.club/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.size.club/docs/cash-games/entry-and-prizes.md). # Entry and cash prizes Choose cash as your reward to compete for the displayed prize. You trade a virtual balance during the game. If you lose, you lose the paid entry. Virtual trading profits are not withdrawable cash. ## Choose an entry Before starting, review: * **Entry:** the amount you pay. * **Difficulty:** the challenge you choose. * **Prize:** the total cash payout for a win. * **Rules:** the scoring and elimination conditions. If you add funds or sign in after choosing, review the selection again before confirming. ## Understand the multiplier Multiply your entry by the payout multiplier to calculate the total prize. The total includes your entry. For example, a $10 entry at 2× pays $20 if you win. That includes your $10 entry and $10 winnings, before additional charges. A multiplier describes the payout, not your chance of winning. A 2× payout does not mean a 50% win chance. See [Costs and fees](/docs/wallet/costs-and-fees.md) for charges, or [Game rules](/docs/gameplay/game-rules.md) for how to win. --- # 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://www.size.club/docs/cash-games/entry-and-prizes.md?ask=&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.