> For the complete documentation index, see [llms.txt](https://docs.wagercasino.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wagercasino.io/whitepaper/iii.platform-offering/same-game-parlay.md).

# Same Game Parlay

Elevate your betting strategy with Wager's Same Game Parlay feature, allowing you to combine multiple bets from the same match into one high-value opportunity. Create your perfect parlay by mixing player props, game totals, and match outcomes – all while enjoying boosted odds and our industry-leading early payout terms.

* Mix markets from the same game
* Combine player props, team totals and match results
* No restrictions on number of bets
* Earn Wager Credits on all bets
* Share bet URL for social parlay sharing&#x20;

<figure><img src="/files/3GTZEplyQohPXDWFjo6R" alt="" width="563"><figcaption></figcaption></figure>


---

# 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.wagercasino.io/whitepaper/iii.platform-offering/same-game-parlay.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.
