> For the complete documentation index, see [llms.txt](https://docs.decider.market/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decider.market/documentation/resolution-and-data/event-based-markets.md).

# Event-Based Markets

Event-based markets resolve on real-world outcomes — elections, listings, dates, and similar events.

## The source

These markets use **official public results** as their source: election commissions, exchange announcements, and other authoritative publishers.

## How they resolve

1. The event's official result is published.
2. The resolver (admin/dev) verifies the result against the official source and cross-checks it.
3. The resolver calls `resolve(winner)` via the admin-only API endpoint.

## Why humans are involved

Unlike price markets, event outcomes are not automatically readable from a feed. A human resolver judges the result from the official source, which is why resolution is centralized and why the resolution source is declared upfront.

{% hint style="warning" %}
Because event markets rely on human judgment of an official source, the resolver's honesty is the key trust assumption. See Resolver Risk.
{% endhint %}


---

# 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.decider.market/documentation/resolution-and-data/event-based-markets.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.