Meta headcount, Q2 2026 [ resolved 2026-07-29 ]
kalshi: [C] single source·objective outcome methodology ›
distribution · by outcome · marks: daily snapshot
kalshi 18 markets
| market | resolves | P(YES) | vol (24h) | vol (cum) | RCG | venue id | ||
|---|---|---|---|---|---|---|---|---|
| > 70000 | 2026-07-29 | 100.0% | $242 | $377 | C | KXMETA-26SEP…000 | ||
| > 70500 | 2026-07-29 | 100.0% | $119 | $287 | C | KXMETA-26SEP…500 | ||
| > 71000 | 2026-07-29 | 100.0% | $146 | $330 | C | KXMETA-26SEP…000 | ||
| > 71500 | 2026-07-29 | 100.0% | $10 | $282 | C | KXMETA-26SEP…500 | ||
| > 72000 | 2026-07-29 | 100.0% | $78 | $82 | C | KXMETA-26SEP…000 | ||
| > 72500 | 2026-07-29 | 100.0% | $147 | $299 | C | KXMETA-26SEP…500 | ||
| > 73000 | 2026-07-29 | 100.0% | $247 | $12K | C | KXMETA-26SEP…000 | ||
| > 73500 | 2026-07-29 | 100.0% | $114 | $4.0K | C | KXMETA-26SEP…500 | ||
| > 74000 | 2026-07-29 | 100.0% | $600 | $7.0K | C | KXMETA-26SEP…000 | ||
| > 74500 | 2026-07-29 | 100.0% | $538 | $7.1K | C | KXMETA-26SEP…500 | ||
| > 75000 | 2026-07-29 | 100.0% | $349 | $5.3K | C | KXMETA-26SEP…000 | ||
| > 75500 | 2026-07-29 | 0.0% | $247 | $2.5K | C | KXMETA-26SEP…500 | ||
| > 76000 | 2026-07-29 | 0.0% | $355 | $3.0K | C | KXMETA-26SEP…000 | ||
| > 76500 | 2026-07-29 | 0.0% | $212 | $1.5K | C | KXMETA-26SEP…500 | ||
| > 77000 | 2026-07-29 | 0.0% | $36 | $213 | C | KXMETA-26SEP…000 | ||
| > 77500 | 2026-07-29 | 0.0% | $7 | $21 | C | KXMETA-26SEP…500 | ||
| > 78000 | 2026-07-29 | 0.0% | — | $0 | C | KXMETA-26SEP…000 | ||
| > 78500 | 2026-07-29 | 0.0% | $5 | $5 | C | KXMETA-26SEP…500 |
resolution architecture
| venue | proposer | source | citation | arbitration | class | analyst notes |
|---|---|---|---|---|---|---|
| kalshi | Exchange Staff | Fiscal.ai | not provided | Kalshi Staff | Other | — |
verbatim rules
kalshi
If Meta Platforms, Inc. reports above 70000 Headcount in Q2 2026, then the market resolves to Yes.
platform source field
kalshi.settlement_sources → "Fiscal.ai" sources (1) · single authority
Fiscal.ai committed source
resolution history
| outcome | market | venue | resolved | final price |
|---|---|---|---|---|
| YES | Will Meta Platforms, Inc. report above 70000 Headcount in Q2 2026? | kalshi | 2026-07-29 | 100% |
| YES | Will Meta Platforms, Inc. report above 70500 Headcount in Q2 2026? | kalshi | 2026-07-29 | 100% |
| YES | Will Meta Platforms, Inc. report above 71000 Headcount in Q2 2026? | kalshi | 2026-07-29 | 100% |
| YES | Will Meta Platforms, Inc. report above 71500 Headcount in Q2 2026? | kalshi | 2026-07-29 | 100% |
| YES | Will Meta Platforms, Inc. report above 72000 Headcount in Q2 2026? | kalshi | 2026-07-29 | 100% |
| YES | Will Meta Platforms, Inc. report above 72500 Headcount in Q2 2026? | kalshi | 2026-07-29 | 100% |
| YES | Will Meta Platforms, Inc. report above 73000 Headcount in Q2 2026? | kalshi | 2026-07-29 | 100% |
| YES | Will Meta Platforms, Inc. report above 73500 Headcount in Q2 2026? | kalshi | 2026-07-29 | 100% |
| YES | Will Meta Platforms, Inc. report above 74000 Headcount in Q2 2026? | kalshi | 2026-07-29 | 100% |
| YES | Will Meta Platforms, Inc. report Above 74500 Headcount in Q2 2026? | kalshi | 2026-07-29 | 100% |
| YES | Will Meta Platforms, Inc. report Above 75000 Headcount in Q2 2026? | kalshi | 2026-07-29 | 100% |
| NO | Will Meta Platforms, Inc. report Above 75500 Headcount in Q2 2026? | kalshi | 2026-07-29 | 0% |
| NO | Will Meta Platforms, Inc. report Above 76000 Headcount in Q2 2026? | kalshi | 2026-07-29 | 0% |
| NO | Will Meta Platforms, Inc. report Above 76500 Headcount in Q2 2026? | kalshi | 2026-07-29 | 0% |
| NO | Will Meta Platforms, Inc. report Above 77000 Headcount in Q2 2026? | kalshi | 2026-07-29 | 0% |
| NO | Will Meta Platforms, Inc. report Above 77500 Headcount in Q2 2026? | kalshi | 2026-07-29 | 0% |
| NO | Will Meta Platforms, Inc. report Above 78000 Headcount in Q2 2026? | kalshi | 2026-07-29 | 0% |
| NO | Will Meta Platforms, Inc. report Above 78500 Headcount in Q2 2026? | kalshi | 2026-07-29 | 0% |
Resolution dates are the venue's settlement timestamps (18 resolved markets). Rows shown as "by [date]" carry the contract deadline: the venue no longer exposes a settlement time for them. PENDING upgrades to a final outcome on the next refresh.
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/kxmeta-26sephead/ |
| JSON | REST API for developers | https://api.clearmarket.fyi/v1/events/kxmeta-26sephead |
| MCP | agentic AI tool call (Claude Desktop, Cursor, Continue) | clearmarket.get_event("kxmeta-26sephead") |
| AGENT | AI crawler discovery index | /llms.txt |
Snapshot 2026-08-04. 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-T7THY5BG33",
"slug": "kxmeta-26sephead",
"question": "Meta headcount, Q2 2026",
"category": "financials",
"tags": [
"financials",
"meta-headcount",
"q2-2026",
"corporate-employment",
"financial-metrics",
"tech-sector"
],
"venues_covered": [
"kalshi"
],
"market_count": 18,
"cumulative_volume_usd": 44256,
"resolution_clarity_grade": "C",
"rcg_score": 90,
"rcg_caps": [
"commitment_committed_secondhand"
],
"resolution_source": "Fiscal.ai",
"resolution_source_url": "https://fiscal.ai",
"source_status": "platform_named",
"source_of_record": "Fiscal.ai",
"resolution_source_list": [
{
"name": "Fiscal.ai",
"url": "https://fiscal.ai",
"provenance": "platform_api"
}
],
"arbitration_model": "kalshi_staff",
"proposer_model": "platform_staff",
"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"
}
}
}