Event Resolver API

io.github.Br0ski777Published by GitHub account Br0ski777v1.1.0Updated Oct 24, 2026

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

VerifiedSSEWeb executableWeb Search & ScrapingFinance

Overview

AI-generated overview

Remote MCP server that resolves prediction market events, verifies factual claims, and checks price thresholds, returning outcomes with confidence scores.

What you can do
  • Resolve a real-world event question as binary, numeric, or categorical, with outcome, confidence score, and consulted sources
  • Quickly verify a factual claim and get a true, false, or unverifiable verdict with confidence and evidence
  • Check whether a crypto or stock price has crossed a given USD threshold in a chosen direction
  • Each call is billed per use through x402 micropayments
When to use it
Useful when an assistant needs to settle or sanity-check prediction market questions, confirm whether a real-world event happened, or test a price threshold condition, without building its own data aggregation pipeline.
Requirements
A remote MCP endpoint; no API key or signup. Calls are paid per request in USDC on Base L2 via the x402 protocol, so an x402-capable client or wallet that can sign the payment challenge is needed. Network access to the provider is required.
Before you install
Every tool call costs money (roughly $0.005 to $0.012 per call in USDC on Base), so automated or looping use can spend funds from the connected wallet. Payment is handled by third-party facilitators, and questions and claims are sent to the provider and its upstream data sources. Results are confidence-scored estimates, not authoritative settlement.

Installation

In SourceWeft

  1. Open Event Resolver API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Br0ski777%2Fevent-resolver/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

Event Resolver API

[MCP Server] [x402] [License: MIT]

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.):

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

Quickstart -- HTTP (x402)

bash
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:

json
{ "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:

json
{ "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:

json
{ "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

Source: README.md at commit 119cb1a

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts