Event Resolver API

Official registry E-commerce

Resolve prediction market events. Price checks, claim verification, outcome confidence.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (sse)
Claude Code
claude mcp add --transport sse event-resolver-api 'https://event-resolver.api.klymax402.com/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "event-resolver-api": {
            "type": "sse",
            "url": "https://event-resolver.api.klymax402.com/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Event Resolver API
  2. Quickstart -- MCP
  3. Quickstart -- HTTP (x402)
  4. Tools
  5. Example agent prompts
  6. Payment
  7. Part of klymax402
  8. License

Event Resolver API

Resolve prediction market events with confidence scores. Aggregates news, price feeds, and web data to determine if real-world events occurred. Settlement oracle for binary, numeric, and categorical outcomes. Pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.

Part of the klymax402 marketplace -- 100 x402 micropayment APIs for AI agents, one wallet, USDC on Base.

Quickstart -- MCP

Add to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.):

{
  "mcpServers": {
    "event-resolver": {
      "url": "https://event-resolver.api.klymax402.com/mcp"
    }
  }
}

Quickstart -- HTTP (x402)

curl -X POST "https://event-resolver.api.klymax402.com/api/resolve" \
  -H "Content-Type: application/json" \
  -d '{"question":"..."}'
# -> 402 Payment Required, with an x402 payment challenge in the response body

Any x402-aware client (@x402/fetch, x402-agent-tools, ATXP) handles the 402 -> sign -> retry cycle automatically.

Tools

ToolMethodPathPriceDescription
event_resolve_outcomePOST/api/resolve$0.012Resolve a prediction market event/question. Aggregates multiple data sources to determine outcome with confidence score.
event_verify_claimPOST/api/verify$0.008Quick-verify a factual claim. Returns verdict (true/false/unverifiable) with confidence and evidence.
event_check_price_thresholdPOST/api/price-check$0.005Check if a crypto/stock price crossed a threshold. Common prediction market resolution pattern.
event_resolve_outcome

Use this when you need to determine the outcome of a real-world event for prediction market settlement. Takes a natural language question (e.g. "Did BTC reach $100K?", "Did France win the 2026 World Cup?") and returns a structured resolution with confidence score.

Parameters

NameTypeRequiredDescription
questionstringyesThe event question to resolve, e.g. 'Did BTC reach $100K by April 2026?' or 'Did the Lakers win the NBA Finals 2026?'
typestringnoType of resolution expected. binary = Yes/No, numeric = a number, categorical = one of several options. Default: binary.

Returns

  • question -- the original question being resolved
  • resolved -- whether the event can be conclusively determined (true/false)
  • outcome -- the determined result -- "Yes"/"No" for binary, a number for numeric, or a category string
  • confidence -- 0-100 score indicating certainty of the resolution
  • sources -- array of data sources consulted, each with name, url, and whether it agrees with the outcome
  • timestamp -- ISO timestamp of when the resolution was performed

Example response:

{ "question": "Did BTC reach $100K?", "resolved": true, "outcome": "Yes", "confidence": 95, "sources": [{ "name": "CoinGecko", "url": "https://coingecko.com", "agrees": true }], "timestamp": "2026-04-13T12:00:00Z" }

Not for: prediction market odds (use prediction_list_markets), crypto prices only (use token_get_price), full fact checking with sources (use research_check_fact), trust/security scoring (use trust_score_evaluate).

event_verify_claim

Use this when you need to quickly verify whether a factual claim is true or false. Simpler and cheaper than full event resolution -- designed for fast claim checking without structured market settlement.

Parameters

NameTypeRequiredDescription
claimstringyesThe factual claim to verify, e.g. 'Bitcoin is above $90,000' or 'The US unemployment rate is below 4%'

Returns

  • claim -- the original claim being verified
  • verdict -- "true", "false", or "unverifiable" if insufficient data
  • confidence -- 0-100 score indicating certainty of the verdict
  • evidence -- array of strings summarizing supporting or contradicting evidence found

Example response:

{ "claim": "Tesla stock is above $300", "verdict": "true", "confidence": 90, "evidence": ["CoinGecko/financial APIs confirm current price above threshold", "Multiple news sources corroborate"] }

Not for: prediction market odds (use prediction_list_markets), full fact checking with sources (use research_check_fact), stock prices (use stock_get_quote), crypto prices only (use token_get_price).

event_check_price_threshold

Use this when you need to check if a cryptocurrency or stock price has crossed a specific threshold -- the most common resolution type in prediction markets. Returns current price, whether threshold was crossed, and direction.

Parameters

NameTypeRequiredDescription
assetstringyesAsset name or CoinGecko ID (e.g. 'bitcoin', 'ethereum', 'solana', 'dogecoin')
thresholdnumberyesPrice threshold in USD to check against
directionstringyesWhether to check if price is above or below the threshold

Returns

  • asset -- the asset being checked (e.g. "bitcoin", "ethereum", "solana")
  • currentPrice -- the current price in USD from CoinGecko
  • threshold -- the target price threshold
  • direction -- "above" or "below" -- which direction constitutes crossing
  • crossed -- boolean indicating whether the price has crossed the threshold in the specified direction

Example response:

{ "asset": "bitcoin", "currentPrice": 102450.23, "threshold": 100000, "direction": "above", "crossed": true }

Not for: crypto prices only (use token_get_price), prediction market odds (use prediction_list_markets), stock prices (use stock_get_quote), trust/security scoring (use trust_score_evaluate).

Example agent prompts

  • "Determine the outcome of a real-world event for prediction market settlement"
  • "Quickly verify whether a factual claim is true or false"
  • "Check if a cryptocurrency or stock price has crossed a specific threshold -- the most common resolution type in prediction markets"

Payment

  • Protocol: x402 -- HTTP-native pay-per-call, no signup, no API key
  • Network: Base L2 (eip155:8453)
  • Asset: USDC
  • Facilitator: Coinbase CDP (primary), PayAI (fallback)
  • Also reachable via ATXP (OAuth-wrapped x402, RFC 9728 protected-resource metadata)

Part of klymax402

100 x402 micropayment APIs for AI agents -- one wallet, USDC on Base, zero signup.

License

MIT

Frequently asked questions

What is Event Resolver API?

Resolve prediction market events. Price checks, claim verification, outcome confidence.

How do I install Event Resolver API?

It runs as a remote server. In Claude Code: claude mcp add --transport sse event-resolver-api 'https://event-resolver.api.klymax402.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Event Resolver API need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Event Resolver API open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Event Resolver API?

It is published by Br0ski777. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.