Plans and access

Developer SandboxEvaluate
$0 / month

Test requests and response handling with delayed signal data.

1,000requests / month
60requests / minute
  • 15-minute delayed qualified signals
  • Current market and sibling context
  • One active API key
  • Common source-aware response schema
  • Historical snapshots or article archive
  • Live SSE or webhooks
Create sandbox account
Pro IntelligenceMonthly
$30 / month

Live signals, retained history, article records, and event context.

1Mrequests / month
600requests / minute
  • Live canonical signals by REST and SSE
  • Available retained market and article archive
  • Event, sibling, and comparable-move context
  • Customer-side MCP access
  • One HMAC-signed webhook
  • One active API key
Subscribe
Payment flowSign in with Google to subscribe. Dodo Payments confirms the transaction server-side before the selected API entitlement and key limits become active.
Archive coveragePaid historical routes expose all retained data currently available. Historical trajectories are currently Polymarket; Kalshi live-signal coverage follows bounded public trade activity.
Signal qualificationFiltered before delivery
Movement evidenceBaseline, current probability, and delta
Stable identitySource, market_id, event_id, and URL
Event contextRelated outcomes when the source links them
LifecycleDetected, qualified, curated, published, updated, and retired

Event-level context for related markets.

Each record retains its source event ID, so clients can review the lead move beside every related outcome.

Markets sharing one event_id
Candidate A wins primary62%+18
Candidate B wins primary31%-14
Candidate C wins primary7%-4
Output

One event-level record.

Keep the lead move and its related shifts together instead of returning disconnected records for the same event.

market_idevent_idquestionprobabilityobserved_at
Important boundary: sibling records provide event grouping and co-movement context. OddsQ does not label them as arbitrage, guarantee tradeability, or promise an execution edge.

Use cases.

01 / NEWSROOMS

Newsroom monitoring

Monitor qualified shifts, pull a source URL, and use sibling context to write one accurate event-level update instead of duplicating outcomes.

02 / RESEARCH

Historical research

Query retained observations with explicit timestamps and probability units. Join market records through stable source and event identifiers.

03 / BUILDERS

Dashboards and agents

Use REST for scheduled pulls, SSE for an open signal feed, or webhooks when your application should react only to configured thresholds.

04 / OPERATIONS

Filtered alerts

Filter by category and movement size, verify signed callbacks, and retain the signal, evidence, and event context in your own workflow.

Architecture Note

OddsQ provides normalized market data, live signals, and webhook infrastructure. Order execution and financial settlement take place directly on underlying source venues.

Endpoints.

GETSandbox delayed / Paid live
/v1/intelligence/events

Read one canonical feed of fast moves, curated stories, and High-Confidence Market transitions. Sandbox results are held back by 15 minutes.

Returns lifecycle, movement, activity, siblings, evidence, provenance, freshness, and an opaque cursor
SSEPro and Institutional
/v1/live/stream

Open a continuous stream filtered by minimum delta and optional categories. Connected and heartbeat events make stream health observable.

Use for live monitors, internal alerting, agents, and downstream enrichment workers
GETAll plans
/v1/markets/{market_id}/context

Resolve the current market record and up to ten related outcomes that share its source event identifier.

Returns source, question, category, event_id, current_probability, metadata_status, siblings[]
GETPro and Institutional
/v1/markets/{market_id}/history

Page through every retained hourly probability, volume, and liquidity observation currently available in the archive.

Returns probability, probability_percent, observed_at, metadata_status, coverage, next_before
GETPro and Institutional
/v1/articles & /v1/articles/{date}

Read complete retained OddsQ stories with linked event, market, lifecycle, and sibling context for newsroom, search, and research workflows.

Returns story_id, market_id, event_id, headline, subtitle, body, related_markets, lifecycle_state, published_at
POSTPro and Institutional
/v1/webhooks/subscribe

Register a public HTTPS callback and your own signing secret. Set minimum delta and volume thresholds per subscription.

Manage with GET /v1/webhooks and DELETE /v1/webhooks/{subscription_id}
GETInstitutional
/v1/signals/{signal_id}/context

Inspect the stored 10-second tick buffer attached to a qualified signal when deeper evidence is needed for review or modeling.

Returns signal_id, market_id, category, detected_at, count, ticks[]

Request builder.

Choose an endpoint to generate a request and inspect its response shape. Entering a key enables same-origin GET requests; the key stays in this page and is never persisted.

OddsQ API request builder
X-OddsQ-Key
Request
ResponseExample 200
Safety: requests run against this page origin. API keys are held only in memory and are not written to localStorage, sessionStorage, cookies, or analytics.