Connection check
verified live · 20h ago
crosswire-polymarket-kalshi-arbitrage
Cross-venue Polymarket+Kalshi arbitrage: resolution mismatch, void risk & settlement divergence.
Tools
2
GitHub stars
—
Installs / wk
—
Licence
—
Transport
streamable-http
Last checked
20h ago
Tools & capabilities
2 toolsRead from the running server on 20h ago.
check_resolution_risk
read-only
modeapi_keymarket_amarket_bnotional_usdcanonical_event_id
Pre-trade safety check for cross-venue event markets (crypto oracle-divergence pairs, metered; World Cup football, free). Flags resolution mismatches, void-rule divergence, scope d… Pre-trade safety check for cross-venue event markets (crypto oracle-divergence pairs, metered; World Cup football, free). Flags resolution mismatches, void-rule divergence, scope differences (e.g. 90-minute vs extra-time; matched vs differing strike), settlement-source and -timing gaps, stale data, and thin liquidity between the two Polymarket and Kalshi legs BEFORE you execute both. Returns a machine-readable verdict — execution_verdict: safe / caution / block — inside a full Fungibility & Settlement Audit Object (FSAO) with structured findings, top-level divergence flags, venue rule overrides, fee-adjusted spread, and verdict reasons. Identify the pair by EITHER canonical_event_id (a live pair id from list_covered_events — the metered 'crypto:' inventory rolls daily, so fetch a current id there rather than reusing an old one; the free 'wc26:' World Cup pairs are stable) OR market_a + market_b (one Polymarket conditionId + one Kalshi ticker, order-insensitive). If the pair is not covered, returns a non-error coverage reply (covered: false) naming the covered inventories (free World Cup football + metered crypto pairs) and the coverage cutoff instead of an FSAO.
list_covered_events
read-only