What Match is for
Match is the directory and decision layer of OptionsMatch. Use it to discover venues, understand geo access narratives, compare products, read offers, browse intel, and learn via guides — without needing a live options ticket open. The Match sidebar (desktop) and drawer (mobile) keep catalog and learn surfaces one click away.
Match is not a substitute for a venue’s official onboarding, KYC, or trading UI. It is research chrome: higher cache tolerance on catalog pages, editorial structure, and outbound hops that should always be disclosed when affiliate-backed.
When you are ready for multi-venue marks, IVs, and GEX-style desks, hop to Terminal via /t/{asset}/… — the pair and account chrome stay familiar, but the sidebar becomes desk-oriented.
Venues directory and profiles
Open /venue for the catalog. Each profile under /venue/{slug} combines editorial fit scores and copy with enrichment overlays where available: CoinGecko identity and volume context, DefiLlama options/TVL/fees style metrics, and venue API instrument or status fields for feeds such as Thalex and Paradex.
Best-for SEO surfaces under /venue/best-for/{useCase} group venues by job-to-be-done. Stats leaderboards (where present) rank DefiLlama-linked metrics so you can scan relative activity — still subject to upstream freshness.
Read geo notes and product caveats on the profile, then confirm eligibility and fees on the official site. OptionsMatch does not custody deposits and does not complete KYC for you.
Countries, compare, and find-venue
The /countries hub and /countries/{slug} pages map geo access narratives for traders researching where products are described as available. Treat them as structured research, not a compliance opinion letter. Always verify on the venue’s terms and local rules.
Compare routes (/compare and head-to-head /compare/{a}-vs-{b}) put two venues side by side so you can reason about product shape, fees, and fit before opening accounts. Use them together with terminal multi-venue books when you care about live depth, not only catalog bullets.
The /find-venue wizard walks preferences toward a short list. It is a guided directory experience — still free-first research — not an order router.
Offers, affiliate hops, and disclosure
/offers lists partner deals and promotions. Outbound /go/{slug} paths track affiliate hops to official destinations. Read the affiliate disclosure; understand that OM may be compensated if you sign up through tracked links.
Never enter wallet seeds, private keys, or exchange passwords into OptionsMatch. If a hop lands on an unexpected domain, stop and re-open the venue from a bookmark you trust. Affiliate tracking is not a reason to skip domain verification.
Operators should keep offer metadata accurate and avoid promoting dead or misleading deals during soft launch. Honesty beats aggressive conversion copy.
Intel, education, and docs
/intel surfaces free-layer market and venue intelligence as shipped; any future Pro AI should remain clearly separated rather than spoofed as unlocked. /guides hosts the options curriculum; /education/wallets covers security-first wallet onboarding for on-chain venues.
Platform how-to (this documentation set under /docs) explains product usage and architecture pointers. Curriculum guides explain options theory and desk strategy. Keep the two mental folders separate when filing content or training users.
Account surfaces let signed-in users manage preferences appropriate to the soft-launch stage. Free accounts may unlock extras on a roadmap without converting Match into a paywalled empty shell.
Operator notes for Match content
Plural routes are canonical: /venue, /countries. Legacy singular paths redirect. When adding CMS overrides, preserve seed honesty on scores and enrichment display so operators do not invent live volume that CoinGecko or DefiLlama did not provide.
Match chrome should continue to deep-link into Terminal desks where useful (for example, from a venue profile into a multi-venue book) without blurring custody boundaries. Users research here; they fund elsewhere.
Soft-launch banners belong on Match as much as Terminal: early access, free-first positioning, and feed limitations should be visible before a user assumes institutional SLA.