Turn claims into verifiable markets.
VeriClaim uses adversarial AI agents to forge, critique, and validate prediction-market specs. It supports live AI generation, Firebase persistence, public proof pages, and demo-safe Arc/x402 mock flows for the MVP.
Demo court preview
Three agents, one settlement-ready spec.
Transforms messy claims into binary, time-bound MarketSpecs.
Attacks ambiguity, weak sources, vague deadlines, and bad resolution rules.
Produces the final verdict, score, and settlement-ready resolution rule.
Drafted MarketSpec
Converted the social claim into a binary deadline-based infrastructure question.
Attacked launch ambiguity
Found that launch could mean testnet, beta, or mainnet and requested stricter wording.
Blessed and published
Accepted the revised public-mainnet wording and proof-ready metadata.
How it works
From claim to public MarketSpec in one court flow.
VeriClaim structures market-ready specifications only. It does not create betting markets, execute trades, or provide financial advice.
Submit a claim
AI Court creates a MarketSpec
Critic finds ambiguity
Judge finalizes verdict
Save, challenge, or publish mock Arc proof
Messy input to proof-ready spec
The court turns vague claims into settlement-grade JSON.
VeriClaim preserves deadlines, thresholds, sources, and resolution rules so generated specs can be reviewed, challenged, and shared.
Forger
Transforms messy claims into binary, time-bound MarketSpecs.
Critic
Attacks ambiguity, weak sources, and missing edge cases.
Judge
Produces the verdict, score, and final resolution rule.
Will Arc mainnet become publicly available before October 1, 2026?
{
"source_claim": "Arc mainnet will launch before Q4 2026.",
"canonical_claim": "Arc mainnet will become publicly available before October 1, 2026.",
"market_spec": {
"question": "Will Arc mainnet become publicly available before October 1, 2026?",
"outcomes": [
"YES",
"NO"
],
"deadline": "2026-10-01",
"resolution_source": "Official Arc or Circle announcement",
"resolution_rule": "Resolves YES only if Arc mainnet is publicly available before the deadline. Testnet, devnet, invite-only pilots, or private beta access do not count.",
"edge_cases": [
"A renamed public Arc chain counts if Circle identifies it as Arc mainnet.",
"Testnet updates do not count.",
"Private beta or partner-only access does not count."
]
},
"scores": {
"quality": 94,
"tradability": 87,
"resolutionClarity": 96,
"ambiguity": 8
}
}Sample court trace
Forged, challenged, ruled, anchored.
The visual workflow mirrors the SRS court pipeline: Forger, Critic, Judge, then Arc proof and reputation feedback.
Drafted MarketSpec
Converted the social claim into a binary deadline-based infrastructure question.
Attacked launch ambiguity
Found that launch could mean testnet, beta, or mainnet and requested stricter wording.
Blessed and published
Accepted the revised public-mainnet wording and proof-ready metadata.
Example public proof pages
Browse market specs that are built to be challenged.
Will Arc mainnet become publicly available before October 1, 2026?
Will at least one top-five L2 by total value locked announce native USDC settlement before November 16, 2026?
Will the next U.S. headline CPI year-over-year print published by BLS be below 3.0%?
Built for Agora Agents Hackathon ยท Arc-ready MarketSpec infrastructure
Open-source verification UX for claim quality, challengeable specs, and clearly labeled mock Arc/x402 flows.