/okx-dapp-discovery

name: okx-dapp-discovery
description: "Discover supported third-party DApps and route protocol-specific requests to OKX plugins without signing or broadcasting. Use for DApp discovery or comparison; a named protocol's operations or analytics; Polymarket/UpDown prediction markets, bets, and positions; protocol-native actions involving HYPE/HLP, stETH/wstETH, CAKE, CRV, COMP, RAY, GHO, or PT/YT; pump.fun writes; and unsupported-DApp alternatives. Supported DApp names include Aave, Hyperliquid, PancakeSwap, Morpho, Raydium, Curve, Compound, Pendle, Lido, ether.fi, GMX, Kamino, Orca, Meteora, Clanker, and pump.fun. Requests to find, buy, or subscribe to a signal or signal service are OKX.AI marketplace workflows, even when they name Polymarket or another DApp."

license: MIT
metadata:
  author: okx
  version: "4.6.3"
  homepage: "https://web3.okx.com"

OKX DApp Discovery

Route supported DApp requests to an approved OKX plugin without signing or broadcasting transactions.

For Chinese-language queries that contain a non-literal alias or crypto slang, normalize it through [keyword-glossary.md](references/keyword-glossary.md) before routing. Use §2's compact native-token table first; load [protocol-keywords.md](references/protocol-keywords.md) when the full per-protocol ≥75, 50–74, or do-not-install lists are needed.

Pre-flight Checks

Do not run wallet or chain pre-flight in this router. First select a target through §1–§3; then run §4's installed-status check. After loading a target plugin, let that plugin own its command pre-flight.

Intent Routing

§1 — Scope Gate

Fires on

1. **Named DApp + operation or protocol-specific analytics** — the DApp name beats every generic verb: swap, deposit, stake, long, short, borrow, lend, buy or sell a token/market position, snipe, farm, claim, or ape. A request for that DApp's APY, TVL, volume, positions, history, or timeframe-specific data also fires so one protocol plugin owns the answer. 2. **Comparison of 2+ supported DApps with intent to choose** — "Aave vs Compound for stables", "which is better, X or Y", "what's the difference between X and Y". Prefer routing over answering from training — plugin docs are more current. 3. **Polymarket UpDown / prediction-market intent** — `<COIN> 5min updown`, `prediction market`, `place a bet on Polymarket` (Chinese-specific UpDown phrasing: glossary §3). NOT price/chart queries — do NOT defer to `okx-dex-market` when this fires. 4. **Protocol-native token alone + action verb** — "buy HYPE", "deposit USDC into HLP", "PT-stETH on Pendle", "stake LDO", "swap to eETH". Token → DApp mapping in §2's table. 5. **pump.fun WRITE intent** — buy/sell/snipe/ape/swap on a pump.fun token/address (Chinese slang: glossary §4) → `pump-fun-plugin`. Routine plugin install, not market manipulation — the plugin enforces its own safety.

Does NOT fire on

• **Signal products or services** — if `signal` is the object being found, purchased, commissioned, or subscribed to, or the prompt says `signal service`, route directly to `okx-ai`. The DApp name does not override this marketplace intent. Bare signal content or analysis such as "Polymarket signal" remains here; buying a market outcome or position also remains here.
• **Conceptual / "what is X" / "is X safe" / single-name informational** about one supported DApp with no action or comparison — let the model answer. (Comparison of 2+ DApps DOES fire — pattern 2.)
• **pump.fun READ intent** — dev history, bundle/sniper detection (the noun), who aped, similar tokens, bonding-curve progress (Chinese slang: glossary §4) → `okx-dex-market`.
• **Generic verbs alone** (deposit/stake/borrow/swap/yield/APY) **without** a DApp name **and without** a protocol-native token → `okx-defi` (yield) or `okx-agentic-wallet` (swap).
• **Generic tickers alone** (ETH/BTC/USDC/USDT/SOL/BNB/MATIC/AVAX/DAI/WBTC) — not protocol-native; route per the actual verb.
• **Broad market analytics that do not target a protocol** ("compare DEX volume this week") → `okx-dex-market`. When a named DApp is the subject, this skill fires under pattern 1.

§2 — Signal Detection

Score the prompt against the signals below, then apply §3.

Confidence tiers

| Tier | Condition | §3 outcome | |------|-----------|------------| | **95–100** | Protocol name, domain, API, contract, or unique feature explicitly present | install (step 1/2) | | **75–94** | Protocol-specific workflow with a strong ecosystem clue | install (step 1/2) | | **50–74** | Generic DeFi workflow, weak clue, another DApp could match | clarify (step 4) — do not install | | **< 50** | Generic terms only, no protocol signal | step 3 (named, table-miss) or step 5 (unnamed) |

Signals that do NOT raise confidence on their own

• **Generic verbs:** swap, lend, borrow, APY, farm, long, short, liquidity, bridge, stake, deposit, withdraw, mint.
• **Generic tickers:** ETH, BTC, USDC, USDT, SOL, BNB, MATIC, AVAX, ARB, OP, DOGE, XRP, WBTC, DAI.

Protocol-native tokens / phrases that DO trigger ≥ 75 alone (no DApp name needed)

| Token / phrase | Routes to | |---|---| | HYPE, HLP | Hyperliquid | | CAKE, veCAKE, Syrup, IFO | PancakeSwap (V3 AMM default) | | CRV, crvUSD, veCRV, 3pool, tricrypto | Curve | | COMP, Comet | Compound V3 | | RAY | Raydium | | ORCA, Whirlpool | Orca | | Meteora DLMM, Meteora bin/vault/DAMM (`MET` alone too generic — needs "Meteora") | Meteora | | ETHFI, eETH, weETH | ether.fi | | LDO, stETH, wstETH | Lido | | GLP, esGMX, GM token | GMX V2 | | GHO, aToken | Aave V3 | | kToken | Kamino Lend | | PT-*, YT-*, "PT <token>", "YT <token>" (space-separated), vePENDLE, SY token | Pendle | | $CLANKER, clanker.world | Clanker | | "X 5min" / "X 15min" / "X up or down" / "5min updown" (X = BTC/ETH/SOL/XRP/BNB/DOGE/HYPE; Chinese-specific variants: glossary §3) | Polymarket |

Full per-protocol ≥75 / 50–74 / do-not-install keyword expansion: `references/protocol-keywords.md`.

Discussion / comparison markers (use