Compare · 5 alternatives
Where Mentat fits — and where it doesn't.
Every prediction venue makes a resolution tradeoff. Polymarket and Kalshi centralize it; Augur made it slow; Azuro delegates it; Manifold hands it to the creator. Mentat replaces the trusted arbiter with a zkTLS proof for the common case. These pages lay out the differences honestly — including where the alternatives are the better choice today.
Mentat vs Polymarket
read →The dominant USD-volume prediction market — centralized UMA resolution.
Polymarket is the largest prediction venue by volume, with deep liquidity on politics and events. Resolution depends on UMA optimistic oracle and Polymarket Inc. moderating ambiguous outcomes. Permissionless trading, but market creation is staff-gated and US users are restricted.
Mentat vs Kalshi
read →CFTC-regulated event contracts exchange — US-only, staff-listed markets.
Kalshi is the first US-regulated event contracts venue. Markets are listed by Kalshi staff, settled by Kalshi internal data review, and traded only by KYC US residents. Full compliance overhead and zero permissionless surface.
Mentat vs Azuro
read →Liquidity pool primitive for on-chain bookmakers — not a market protocol itself.
Azuro provides the on-chain liquidity layer that powers third-party sports betting frontends. It is not a prediction market protocol per se but an adjacent infrastructure layer; resolution still depends on the bookmaker's chosen data provider.
Mentat vs Manifold
read →Social prediction markets with play-money mana — community forecasting.
Manifold has the best UX in the space for casual forecasting, with mana as a play-currency. Markets are user-created and resolved by the creator. Not designed for capital-at-risk markets with cryptographic resolution.
Mentat vs Augur
read →The OG decentralized prediction market on Ethereum — REP-based reporter disputes.
Augur pioneered decentralized prediction markets with REP-token reporter dispute rounds. The model proved sound but slow, expensive on Ethereum L1, and chronically illiquid. zkTLS-based settlement skips most of the dispute surface entirely.
At a glance
The one thing that changes.
| Venue | Resolution model | Market creation |
|---|---|---|
| Mentat | zkTLS proof verified on-chain | Permissionless · AI-drafted · curator-gated |
| Polymarket | UMA oracle + Polymarket Inc. | Staff-listed |
| Kalshi | Internal staff review (CFTC) | Staff-listed |
| Azuro | Delegated data provider | Partner-configured |
| Manifold | Creator resolves | Permissionless (play-money) |
| Augur | REP reporter disputes | Permissionless (raw) |
Want the mechanics behind the "zkTLS proof" column? See how it works, or read why zkTLS, not oracles.
Read the code, not the pitch.
The entire stack is MIT. Verify every claim on these pages against the source.