# Free Text & Structure

**For now**, outrights are offered as free-text markets. This will change over time, and more and more of the markets will be offered as structured markets instead. This gives more flexibility for odds-key configuration, and also give better ability to find bet constraints (i.e. two different bets on variations of the same outcome)

Free-text outright markets are market 534 (Championship), 535 (Short-term), 536 (Multi-winner), and 559. These markets have a variant specifier that describes the outright, using the normal variant specifier logic. The SDKs takes care of this automatically.

Structured outright markets was introduced for the Virtual Sports, and Sportradar will follow-up with a transition of some major outrights markets to structured form. These markets will have their own ids and will not use variants. For example, there will be a “Winner of {$event}” market where each outcome is one of the competitors competing in the competition (league, race etc).

Some structured outrights markets have multi-competitor-outcomes. Here more than one competitor is listed in the same outcome, using each competitor’s id separated by comma. This allows the client to detect related bets accurately i.e.:

“Who will win the event – Germany (sr:competitor:1234)” and “What teams will be placed top-3 – Germany(sr:competitor:1234), France, Spain” can be considered related bets as they include the same exact competitor, rather than relying on name-matching, which does not work reliably.

Some structured outrights markets will also use fixed structured outcomes such as “Yes”, “No” and “Over”, “Under”.


---

# Agent Instructions: 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:

```
GET https://docs.sportradar.com/uof/data-and-features/markets-and-outcomes/market-types/free-text-and-structure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.