Will Iran agree to end enrichment of uranium by July 31? [ resolves 2026-07-31 (49D) ]
Iran agrees to end enrichment of uranium by July 31?
polymarket: [C] single source·reporting consensus methodology ›
markets · by resolution date
polymarket 1 market
| market | resolves | P(YES) | vol (24h) | vol (cum) | RCG | venue id | ||
|---|---|---|---|---|---|---|---|---|
| Iran agrees to end enrichment of uranium by July 31 | 2026-07-31 | 29.0% | $7.0K | $35K | C | 0x151b13…f8d4 |
resolution architecture
| venue | proposer | source | citation | arbitration | class | analyst notes |
|---|---|---|---|---|---|---|
| polymarket | Whitelisted Proposers | uncommitted | not provided | Optimistic Oracle (UMA) | Other | — |
verbatim rules
polymarket
This market will resolve to "Yes" if Iran publicly agrees to end all enrichment of uranium by July 31, 2026, 11:59 PM ET. Otherwise, this market will resolve to “No”.
An official pledge by Iran to end all enrichment of Uranium will qualify for a “Yes” resolution, whether as a unilateral announcement or part of an agreement with the U.S. or Israel.
Any agreement or pledge made before the resolution date of this market will qualify, regardless of if/when the agreement goes into effect.
An agreement by Iran to end all enrichment of uranium for any amount of time will count.
An agreement by Iran to end all enrichment of uranium as a precondition of a more comprehensive peace process or deal will qualify, even if the agreement is not finalized or part of a formalized peace deal.
Agreements to merely limit or cap the level or quality of enrichment—such as reducing enrichment to below weapons-grade thresholds—will not qualify.
The primary resolution source for this market will be a consensus of credible reporting.
platform source field
polymarket.resolutionSource → ∅ no committed source — see rules text above recent wire items
monitoring status: active no active wire
No CM Signal wire has been published for this event yet.
CM Signal’s news-cycle scan surfaces the day’s top stories alongside the prediction markets pricing them. When a story references this event, its wire is published here and links back to this page.
programmatic access · four surfaces, same payload
One canonical record at every surface — embedded JSON-LD, REST, MCP, and /llms.txt.
| HTML | browsers, AI grounded search, crawlers (embedded JSON-LD @type: Dataset) | https://clearmarket.fyi/events/iran-agrees-to-end-enrichment-of-uranium-by-july-31/ |
| JSON | REST API for developers | https://api.clearmarket.fyi/v1/events/iran-agrees-to-end-enrichment-of-uranium-by-july-31.json |
| MCP | agentic AI tool call (Claude Desktop, Cursor, Continue) | clearmarket.get_event("iran-agrees-to-end-enrichment-of-uranium-by-july-31") |
| AGENT | AI crawler discovery index | /llms.txt |
Snapshot 2026-06-12. Venue data via Kalshi + Polymarket APIs. Editorial fields (tags, editorial_notes) are ClearMarket-drafted with AI assistance under editorial review. Derived fields (venues_covered, resolution_clarity_grade, rcg_score) computed at serve time. Full per-field map in the JSON record under field_provenance.
raw JSON record · same payload returned by REST endpoint {
"event_id": "CM-EVT-8SWDJJDJM0",
"slug": "iran-agrees-to-end-enrichment-of-uranium-by-july-31",
"question": "Will Iran agree to end enrichment of uranium by July 31?",
"category": "geopolitics",
"tags": [
"iran-nuclear",
"geopolitics",
"diplomacy-agreement",
"2026",
"trump",
"sanctions-relief"
],
"venues_covered": [
"polymarket"
],
"market_count": 1,
"cumulative_volume_usd": 34952,
"resolution_clarity_grade": "C",
"rcg_score": 10,
"rcg_caps": [
"discretionary_trigger_no_source",
"adversarial_ground_truth",
"uncommitted_illustrative"
],
"resolution_source": null,
"resolution_source_url": null,
"arbitration_model": "uma_oracle",
"proposer_model": "managed_whitelist",
"field_provenance": {
"question": {
"source": "clearmarket_editorial"
},
"tags": {
"source": "clearmarket_editorial",
"ai_drafted": true
},
"resolution_clarity_grade": {
"source": "derived",
"method": "rcg_v2_7factor"
},
"venues_covered": {
"source": "derived"
}
}
}