What OptionsMatch is
OptionsMatch is a hybrid research platform for crypto options: a Match layer for venue discovery, geo context, offers, intel, and education, plus a Terminal layer for multi-venue books, volatility, greeks, flow, and charts. It is built for traders and operators who want honest data labeling, free core access, and a path from learning to venue choice without fake paywalls on empty features.
The product family deliberately separates shopping and learning (Match chrome) from live desk work (Terminal chrome under /t/{asset}/…). One app, two jobs — so a venue directory page does not pretend to be an order ticket, and a GEX workbench does not pretend to be a KYC portal.
OptionsMatch does not custody funds, does not ask for wallet seeds or private keys, and does not require API secrets for public research. When you execute, you leave via official venues or disclosed affiliate hops.
Two chromes, one product family
Match is the default marketing and directory layer: home, /venue, /countries, /compare, /find-venue, /offers, /intel, /guides, /docs, account surfaces, and legal pages. Desktop Match uses a persistent sidebar with directory, access, learn, and account groups; mobile uses a drawer. There is no terminal-style bottom tab bar on pure Match routes.
Terminal lives under /t/{asset}/… with desk tools — dashboard, book/chain, GEX, term and skew, tape and flow, charts hubs, calculator, custom dashboard, sources, and related volatility or greeks desks. Terminal chrome adds a desk sidebar and, on mobile, a bottom nav optimized for pair switching and desk hopping.
Helpers such as terminalHref() build /t/{asset}/… paths; Match helpers build plural catalog paths like /venue/{slug} and /countries/{slug}. Legacy singular routes redirect. Soft-launch banners and early-access labeling stay honest about what is free, experimental, or feed-degraded.
Free-first and affiliate positioning
Core research is free-first: venue profiles, multi-venue visibility where public APIs allow, education curriculum, and platform docs. Monetization leans on affiliate /go hops and brand partnerships rather than locking empty “Pro” screens behind a credit card wall.
Pro or whitelist-gated experiments may exist for admin and early operators; they should be labeled as such. Intel free layers and any future Pro AI features are meant to stay clearly separated when shipped — no faux unlock of capabilities that are not built.
Always read affiliate disclosures on offers and outbound paths. OptionsMatch tracks hops for partners; it does not take custody of your deposits on the destination venue.
Live data vs mock labeling
Terminal merges normalize venue quotes into shared chain snapshots. Live data is preferred when adapters and upstream APIs are healthy. Mock or placeholder fills are used only when needed for layout continuity and must be labeled so desks do not silently trade on fiction.
The sources desk and on-desk indicators surface up, degraded, or down states for venues such as Deribit, Bybit, OKX, Binance, Derive, Thalex, and Paradex depending on asset coverage and API health. Thalex public REST can hit rate or geo blocks in some environments; Paradex markets/summary style feeds power options rows when available — both should be reported honestly.
Operators and users should treat degraded labels as first-class information: slow down, cross-check the venue UI, and do not invent certainty from a partial merge.
Enrichment and directory intelligence
Venue profiles combine editorial scores and copy with enrichment from CoinGecko (exchange identity, 24h volume fields, trust and metadata where mapped) and DefiLlama (options volume, fees, revenue, TVL, token metrics where mapped). Snapshots can land in durable enrichment storage via operator enrich jobs.
Venue REST contributes instrument counts and status for feeds such as Thalex and Paradex when pipelines succeed. Missing enrichment is not the same as a missing venue — editorial seed data still powers navigation while live fields catch up.
Country pages and find-venue flows help with geo access narratives; they are research aids, not legal advice. Confirm eligibility on the venue’s official terms.
Where to start (users)
New traders: start with /guides curriculum and /education/wallets before any on-chain deposit. Venue shoppers: /venue, /compare, and /find-venue. Active desks: /t/btc/dashboard or the book/chain desks for your pair.
Security-sensitive onboarding (Derive, Paradex): read wallet guides first, then venue profiles, then official site bookmarks only. OptionsMatch remains read-only research throughout.
Operators: use platform docs in this section, the runbook, and soft-launch notes for labeling, affiliate honesty, and feed health expectations.
Where to start (operators)
Know the dual chrome boundary: Match routes versus /t terminal routes, and which nav constants drive each shell. Monitor sources health and enrichment jobs; prefer degraded truth over silent mock pollution on public desks.
Keep soft-launch defaults and disclosures aligned with STAGE_E and RUNBOOK practice: legal pages present, affiliate disclosure visible, early-access messaging accurate. Do not advertise Pro AI or paywalled depth that is not shipped.
When documenting new desks or venues, update user-facing platform docs and education links so operators and end users share the same mental model of free-first research plus official-venue execution.