Prediction Markets Events

Available as MCP tools: polymarket_event_browse + polymarket_event_search + polymarket_event_read - call directly from Claude / Cursor / any MCP client. See MCP Server for the 60-second setup.

Live 1 credit · browse 2 credits · search free · read

What it does for your agent

Prediction Markets events group related market questions into one agent-readable card. Use polymarket_event_search for natural-language questions such as “Bitcoin ETF approval” or “Fed rate cut odds”; use polymarket_event_browse only for list requests or exact filters such as q=ETF, tag=policy, or min_volume=10000. The event card is the entry point, not the final stop. After browse or search returns an event_card_id, call polymarket_event_read to load the event description, lifecycle state, tags, and child market previews before choosing a market.

Agent flow

Response

Browse and search response

PolymarketEvent[]

required

Browse results use lifecycle and liquidity ordering. Search results use semantic relevance.

Show PolymarketEvent fields

string

required

Stable LLMQuant event id. Pass this to polymarket_event_read.

string

required

Human-readable event title.

string

Event-level description when available.

number

required

Number of child markets in the event card.

PolymarketMarketPreview[]

required

Market previews with market_card_id, market_question, outcomes, status, liquidity, and volume.

string[]

required

Finance tags such as crypto, policy, or macro.

string

required

Event status: active, inactive, or closed.

string

required

Coverage state for this normalized event card.

number

Present on semantic search results. Higher means closer to the query.

number

Number of returned events.

string

Pagination cursor for browse, when more events are available.

string

Always finance for this product surface.

number

1 for browse and 2 for search.

number

Account credits remaining.

200 OK · event search

{
  "data": {
    "events": [
      {
        "event_card_id": "4b8f35c6-4781-4f3c-9237-142fc16467cd",
        "title": "Bitcoin ETF approved by Jan 15?",
        "description": "Markets related to whether a spot Bitcoin ETF is approved.",
        "market_count": 1,
        "markets": [
          {
            "market_card_id": "e370488a-33b5-4abd-8c5c-37c7ad8a60fc",
            "market_question": "Bitcoin ETF approved by Jan 15?",
            "outcomes": [
              { "label": "Yes", "outcome_token_id": "98787006152320761811798607481686168525551752574583108841982899511109091268658", "current_probability": 0.51 }
            ],
            "status": "closed",
            "volume": 1250000,
            "liquidity": 48000
          }
        ],
        "tags": ["crypto", "etf"],
        "status": "closed",
        "coverage_status": "partial",
        "semantic_score": 0.91
      }
    ],
    "count": 1,
    "scope": "finance"
  },
  "meta": { "creditsUsed": 2, "remainingCredits": 98 }
}

Event read response

PolymarketEvent

required

One event card with the same fields returned by browse/search, plus full event metadata.

number

Always 0 for event read.

number

Account credits remaining.

Notes

Use search for user language. Use browse only for explicit list or exact lexical filters (status=active, q=ETF, min_volume=10000). Read the selected event before choosing a market so the agent sees all child questions together.

For market-level outcomes and probability history, continue to Prediction Markets Market Details with the market_card_id returned in the event card.

This surface is finance-scoped. It does not cover sports, entertainment, wallet state, order books, or trading actions.

start_time and end_time must be used together, and start_time cannot be after end_time.

Direct invocation

HTTP / SDK examples

// 1) Search for an event
{
  "method": "tools/call",
  "params": {
    "name": "polymarket_event_search",
    "arguments": { "query": "Bitcoin ETF approval", "status": "active_or_recently_closed", "limit": 5 }
  }
}

// 2) Read the selected event
{
  "method": "tools/call",
  "params": {
    "name": "polymarket_event_read",
    "arguments": { "event_card_id": "pme_902959" }
  }
}

import os, requests

base = "https://api.llmquantdata.com"
headers = {"Authorization": f"Bearer {os.environ['LLMQUANT_API_KEY']}"}

events = requests.post(
    f"{base}/api/polymarket/events/search",
    headers=headers,
    json={"query": "Bitcoin ETF approval", "status": "active_or_recently_closed", "limit": 5},
).json()["data"]["events"]

event = requests.get(
    f"{base}/api/polymarket/events/{events[0]['event_card_id']}",
    headers=headers,
).json()["data"]
print(event["title"], event["market_count"])

curl -X POST "https://api.llmquantdata.com/api/polymarket/events/search" \
  -H "Authorization: Bearer $LLMQUANT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "Bitcoin ETF approval", "status": "active_or_recently_closed", "limit": 5}'

curl "https://api.llmquantdata.com/api/polymarket/events/pme_902959" \
  -H "Authorization: Bearer $LLMQUANT_API_KEY"

Full parameter reference

polymarket_event_browse — request parameters

string

default:"active"

One of active, inactive, closed, or active_or_recently_closed.

string

Optional exact lexical filter across event title, slug, tags, child market questions, and outcome labels. Max 200 characters.

string

Optional finance tag, such as crypto or policy.

string

Optional asset or entity filter, such as BTC.

string

ISO 8601 UTC start. Must be used with end_time.

string

ISO 8601 UTC end. Must be used with start_time.

number

Optional minimum event-level market volume.

number

Optional minimum event-level market liquidity.

number

default:20

Maximum events returned. Range 1-100.

string

Pagination cursor from data.nextCursor.

polymarket_event_search — request parameters

string

required

Natural-language query. Max 2,000 characters.

string

default:"active_or_recently_closed"

One of active, inactive, closed, or active_or_recently_closed.

string

Optional finance tag.

string

ISO 8601 UTC start. Must be used with end_time.

string

ISO 8601 UTC end. Must be used with start_time.

number

default:5

Maximum events returned. Range 1-20.

polymarket_event_read — request parameters

string

required

Event id returned by browse or search; the alias pme_902959 is also accepted.

Prediction Markets Market Details

Read market outcomes and implied-probability history.

MCP Server setup

Connect Claude / Cursor / any harness in 60 seconds.

Getting Started

Connect

Personal Context

Knowledge Data

Crypto Prices