A Zelenskyy-Putin China meeting before 2027 stays at 0%
- Polymarket prices the meeting at 0%, traders see no credible path to a China-hosted summit before year-end.
- 27% of all-time volume in 24h ($23K), a meaningful activity spike for a contract already at the floor.
- Volume at a 0% price typically reflects either settlement anticipation or a news item that killed residual hope.
- Resolves if Zelenskyy and Putin hold a face-to-face meeting on Chinese soil before January 1, 2027.
The model, prompt version, and confidence behind this wire are published below — so you can see how it was judged, and re-check it yourself.
- judge_engine
llm_judge_cm_signal_v1- judge_verdict
- wire_eligible
- judge_confidence
- 0.81 / 1.00
- prompt_template
volume_spike_v1github · auditable
Every wire traces back to the ClearMarket event it is built on, and out to each venue’s own market page — so any figure here can be verified at its source.
- venue_a
- polymarket · 0x1219cce4580ec8af8b9e927915de1f46daf8109d88696f3b6295f45384f714a4
AI grounded search reads embedded JSON-LD in HTML. Developers query REST. Agentic AI clients (Claude Desktop, Cursor) call MCP tools. AI crawlers index via /llms.txt. Same canonical record at every surface.
| HTML | browsers, AI grounded search, crawlers (contains embedded JSON-LD @type: Dataset) | https://clearmarket.fyi/signals/will-zelenskyy-and-putin-meet-next-in-ch-vol-23121/ |
| JSON | REST API for developers | https://clearmarket.fyi/signals/will-zelenskyy-and-putin-meet-next-in-ch-vol-23121.json |
| MCP | agentic AI tool call (Claude Desktop, Cursor, Continue) | clearmarket.get_signal("will-zelenskyy-and-putin-meet-next-in-ch-vol-23121") |
| AGENT | AI crawler discovery index | /llms.txt |
PM data: platform APIs (hourly refresh). News context: retrieved with source citations. Editorial judgment: LLM judge with prompt template versioned per wire type. Per-claim provenance inline above; full per-field provenance map at the JSON endpoint under field_provenance.
raw JSON record · same payload returned by REST endpoint {
"$schema": "https://clearmarket.fyi/schema/signal/v1.json",
"provenance_version": "0.2.0",
"record_id": "CMSIG20260818VS05",
"published_at": "2026-08-18T08:31:22+00:00",
"detection": "volume_spike",
"category_tag": "VOLUME_SPIKE",
"secondary_tags": [],
"pre_news_classification": "pre_news",
"target_event_id": "CM-EVT-RRTJG4DGV7",
"target_event_slug": "where-will-zelenskyy-and-putin-meet-next",
"event_question": "Will Zelenskyy and Putin meet before 2027?",
"bullets": [
"Polymarket prices the meeting at 0%, traders see no credible path to a China-hosted summit before year-end.",
"27% of all-time volume in 24h ($23K), a meaningful activity spike for a contract already at the floor.",
"Volume at a 0% price typically reflects either settlement anticipation or a news item that killed residual hope.",
"Resolves if Zelenskyy and Putin hold a face-to-face meeting on Chinese soil before January 1, 2027."
],
"atomic_claims": [
{
"type": "volume_anomaly",
"provenance": "24h + cumulative volume direct from polymarket API; intensity = 24h/cumulative (derived)",
"field_provenance": {
"volume_24h_usd": {
"tier": "direct",
"method": "polymarket_api"
},
"intensity": {
"tier": "derived",
"method": "arithmetic",
"inputs": [
"volume_24h_usd",
"volume_cumulative_usd"
]
}
},
"liquidity_context": {
"poly_vol_24h_usd": 23121.526
}
}
],
"evaluation": {
"judge_engine": "llm_judge_cm_signal_v1",
"judge_verdict": "wire_eligible",
"judge_confidence": 0.81,
"prompt_template": "volume_spike_v1"
},
"citations": {
"internal": {
"cm_event": "/events/where-will-zelenskyy-and-putin-meet-next/",
"related": []
},
"external": {
"venue_a": null,
"venue_b": null,
"benchmark": null
}
},
"sources": [
{
"label": "ClearMarket market record: Will Zelenskyy and Putin meet before 2027?",
"url": "https://clearmarket.fyi/events/where-will-zelenskyy-and-putin-meet-next",
"retrieved_at": "2026-08-18T08:31:22+00:00"
}
],
"field_provenance": {
"pm_data": "polymarket_api",
"news_context": "retrieval_grounded",
"editorial_judgment": "cm_signal_llm_judge"
}
}
PROVENANCE PROTOCOL v0.2 · [direct] venue api · [mediated] grounded web fetch + source url · [derived] computed from listed inputs · [editorial] versioned llm judgment · full spec /schema/provenance/v1