<!-- canonical: https://docs.melee.markets/resolver-api | markdown: https://docs.melee.markets/resolver-api.md | index: https://docs.melee.markets/llms.txt -->
# Resolver API — Overview

| | |
|---|---|
| Status | Available on devnet |
| Devnet API | `https://api.dev.melee.markets/api/resolver/v1/` |
| Mainnet API | coming soon |
| Program ids | per market, validated against `GET /platform/programs` — they change; see [Environments](/resolver-api/environments#program-ids) |

A **resolver** is an external party that decides the outcome of Melee markets. You register once, tell us how
you want to be notified, expose a small set of HTTP endpoints under one base URL, **approve each market before
it is created**, and when a market's event has concluded you sign a transaction we build for you that records
the result on-chain.

## Things to know before reading further

- **Every market you resolve is one you explicitly accepted.** A creator picks you from the catalogue and
  drafts a market; we send you the draft; you return a confidence score and optionally an edited version; the
  creator accepts your version or walks away. Nothing is created on-chain until you have accepted the exact
  text, and nothing launches until you have acknowledged that the on-chain result matches it.
- **Markets stay open for trading until they are actually resolved.** Proposing a result does not stop
  trading. Only the final resolve (or void) does.
- **Resolution has at most two steps.** *Propose* records an intended result. *Resolve* commits it. If you
  do not support disputes, we combine both into a single transaction for you.
- **Void is a valid result.** Voiding refunds traders. Use it when the underlying event is cancelled or the
  question cannot be answered.
- **Melee can void a market, but never for time.** Melee holds a *void authority* on every market, which the
  program lets it use only from the market's `timeoutTs`. Melee uses it under a
  [published policy](/resolver-api/lifecycles#platform-void): the market's definition or authorities drifted
  from what you accepted, or an operator intervenes (for example when Melee suspends a resolver). A market that is
  late is never voided for it. You are notified when it happens.
- **Your keys are bound to each market at creation and cannot be changed for that market.** Changing the keys
  on your record is coming soon and will affect only markets created afterwards.
- **You sign, you pay.** Transactions we return are unsigned. By default your resolver key is also the fee
  payer; you may name a different payer key of your own.

## How the pieces fit

```mermaid
flowchart LR
    R[Your resolver service] -- register and activate --> M[Melee Resolver API]
    M -- evaluate, accept, live --> R
    M -- trigger callback and status polls --> R
    R -- propose, resolve, void --> M
    M -- unsigned transaction --> R
    R -- signed transaction --> M
    M -- broadcast --> S[(Solana)]
    M -- lifecycle notifications --> R
```

## Where to go next

0. [Your responsibilities](/resolver-api/expectations) and [Environments & testing](/resolver-api/environments).
1. [Registration](/resolver-api/registration), [Keys](/resolver-api/keys), [Fees](/resolver-api/fees).
2. [Market acceptance](/resolver-api/acceptance) — how a market becomes yours.
3. [Changes to a market](/resolver-api/changes) and [Lifecycle notifications](/resolver-api/lifecycle).
4. [Melee Resolver API](/resolver-api/api) and [Endpoints you implement](/resolver-api/your-endpoints).
5. [Verifying the definition](/resolver-api/definition), [Integration reference](/resolver-api/reference)
   (byte-exact signing, hashing, PDA derivation, test vectors), [Resolution walk-throughs](/resolver-api/lifecycles),
   [Failure modes](/resolver-api/errors).
