Two data jobs: directory vs desk
OptionsMatch uses public data in two related ways. Match profiles and stats pages need enrichment — identity, volume, TVL, fees, instrument counts — so directory pages feel current. Terminal desks need normalized options chain snapshots — marks, IVs, greeks, OI — so multi-venue books are comparable.
Those pipelines share venue identity concepts but different refresh and failure modes. A CoinGecko outage can thin profile chrome without zeroing a Deribit chain; a Thalex rate limit can degrade terminal rows without erasing editorial scores.
Honesty rule: prefer explicit degraded or missing states over invented numbers. Soft launch is not a license to silently mock production books.
CoinGecko enrichment
CoinGecko exchange endpoints supply name, launch year, country, URL, image, trust-related fields, 24h BTC volume style metrics, descriptions, and centralized flags for mapped venues (for example deribit, bybit, okx, binance, derive, paradex, coincall via VENUE_EXTERNAL_IDS style maps).
Not every catalog venue has a confirmed CoinGecko id. Thalex, for example, may rely more on venue API plus editorial seed when a CG mapping is absent. UI should tolerate partial enrichment without looking broken.
Operators refresh enrichment via documented enrich jobs (for example enrichVenue / admin POST routes that write snapshots such as .data/venue-enrichment.json). Schedule and rate-limit responsibly against upstream ToS.
DefiLlama enrichment
DefiLlama bundles contribute options volume, fees, revenue, TVL, and token-linked metrics where the protocol or exchange mapping exists. Venue profiles and stats leaderboards use these fields as overlays on editorial content.
DefiLlama is strongest for venues and protocols that publish into its datasets; traditional CEX options desks may be sparse. Absence of DefiLlama fields is a data coverage fact, not proof a venue lacks options products.
Display overlays with source context so users know they are looking at third-party aggregates, not OptionsMatch proprietary tape.
Venue REST: Thalex, Paradex, and CEX adapters
Thalex public REST (instruments, ticker, index) feeds ATM-band ticker caches for chain merge when reachable. Some hosting environments encounter Cloudflare rate or geo blocks; sources should show degraded rather than fabricating quotes. Instrument counts and latency can also enrich profiles.
Paradex markets/summary style endpoints (including ALL style pulls where used) supply marks, IVs, greeks, and open interest into multi-venue chains for supported assets such as BTC, ETH, and HYPE when healthy. Treat appchain performance and API shape as venue-specific, not identical to CEX REST.
CEX adapters (Deribit, Bybit, OKX, Binance, and others as configured) normalize their public option surfaces into the same ChainSnapshot row model. Depth of fields varies by venue — greeks, OI, and order book width are not uniformly available.
Terminal chain merge behavior
Adapters emit normalized rows; merge layers combine venues per asset and expiry/strike grid. Live data wins when present. Mock or placeholder rows fill layout only when required and must remain labeled for users and operators.
Asset coverage follows product configuration — do not assume every venue lists every underlying. Filters on book desks let users focus on venues that matter for a trade idea.
Poll intervals, caching, and backoff on 429s should favor upstream health over aggressive refresh. Soft-launch rate limits are a feature of responsible public API use.
Operator runbook pointers
When profiles look stale, check enrichment job logs and upstream status before editing editorial scores to “fix” volume. When terminal rows vanish, check sources desk and adapter logs before blaming the UI shell.
Document known quirks (Thalex Cloudflare, missing CoinGecko ids, Paradex asset coverage) in internal runbooks and in user-facing copy where it reduces confusion.
Never ask users for API keys or wallet seeds to populate public research. Optional user API keys for personal tooling are a separate product surface and should not be required for Match profiles or labeled public merges.
What users should do with imperfect data
Use OptionsMatch to compare and hypothesize; confirm critical marks and collateral requirements on the venue before size. If a source is degraded, shrink confidence and size, or wait.
Combine enrichment (who is active, rough volume context) with terminal structure (where strikes trade) rather than relying on either alone. Directory heat without book depth is incomplete; book depth without geo and fee context is also incomplete.
Report persistent feed issues through support channels operators publish — include venue, asset, desk, and timestamp so adapters can be diagnosed without sharing secrets.