> For the complete documentation index, see [llms.txt](https://dexsport-3.gitbook.io/dexsport-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dexsport-3.gitbook.io/dexsport-docs/betting/limits.md). # Minimum bet, maximum bet and limits The minimum bet on Dexsport is $1, or the equivalent in the currency you have selected. There is no single maximum, because the ceiling depends on the event: to see it for a specific selection, click the MAX button in the betslip and it shows the largest amount you can stake on it. ![The betslip: the MAX button and the Max. Bet line under the amount field](https://3235441457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZGaNfrspeR8PjegVRwpU%2Fuploads%2Fgit-blob-24e837738d26ac8512343f6e64c04b4d79d81afe%2Fbetslip-max-bet.jpg?alt=media) ## Minimum The minimum stake is $1 or the equivalent in your selected currency. The exact value can vary by event and by currency pool, so check the amount shown on the bet page before you place the bet. A separate number worth remembering is the minimum odds for wagering, which is 1.3. A settled sports or esports bet at odds of 1.3 or higher makes your winnings available for withdrawal. That is a wagering rule, not a betting limit: you can bet at lower odds, the winnings just stay on the non withdrawable balance. ## Maximum The MAX button in the betslip is the reliable answer for any particular selection, because it accounts for the event, the market, and your currency pool. It also accounts for your balance, and it never offers more than you actually have. If the ceiling for the event is $200 and you hold $300, MAX shows $200. If you hold $150, MAX shows $150. On an empty balance it shows 0. So a small number under MAX is not always a limit on the event, sometimes it is the size of your balance. Both numbers are shown at once under the amount field, on the **Max. Bet** line. The first one is the largest stake available to you right now, with your balance taken into account. The second one is the ceiling of the event itself. When the first is lower than the second, the limit is your balance, and an offer to deposit appears under the line. Behind that number, events are split into tiers by how popular the tournament is: the bigger the event, the higher the ceiling. Limits also depend on the account itself, so two players can see different numbers on the same match. The tier is not written anywhere in the interface. You can judge it roughly by the scale of the event, and MAX gives you the exact figure for your account on that selection. ## When a bet does not go through If your stake or your potential winnings run past a limit, the bet is not placed and you see an "Outcome Limit Exceed" error. The usual reasons: * your potential winnings from the event exceed the maximum win limit; * you have too many selections from one event on the slip, so remove one of them; * you are trying to place opposing bets on the same event; * the event is already finished. Lowering the stake or dropping one selection normally solves it. If the maximum win is what blocks you, reducing the amount is the only fix, because the limit applies to the payout and not to the stake. --- # 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://dexsport-3.gitbook.io/dexsport-docs/betting/limits.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.