Metaculus vs Myriad on 2 shared OpenChainBench benchmarks, awaiting live measurements.
AMM prediction market with a keyless public REST API budgeted at 30 requests per 10 seconds. No order book endpoint and no public WebSocket.
Metaculus
No data in window
Myriad
Trails516 ms
Ramp tiers stay well inside documented budgets where they exist, at most 7 percent of Polymarket's published book allowance, and every run aborts at the first sign of sustained errors. This benchmark measures throttle onset behaviour at polite request rates, not maximum venue throughput.
Metaculus
No data in window
Myriad
Trails516 ms
Uptime here means our probes succeeded from three specific regions at a polite request rate. A venue can be up for us and degraded for you, especially during regional network incidents, and a brief blip between probe cycles can go unrecorded. Treat the panel as a measured signal, not a guarantee.
Metaculus and Myriad are compared on 2 shared OpenChainBench benchmarks. See the live table on this page for every metric.
Every benchmark on this page uses the same open methodology, published at https://openchainbench.com/methodology. Data is CC-BY-4.0. Measurement harnesses are MIT-licensed.
Auto-generated pairs require: both providers in the same benchmark for seven consecutive days, at least 1000 samples per provider, observable third-party search demand, and a public /products/[slug] page on OCB. Editorially curated pairs (like this one) may publish early when search demand is high and data is accruing — panels with fewer than 100 samples are shown as provisional. The full pair ledger is versioned in the public repo.