/okx

name: okx
description: Build Solana trading and intelligence applications combining OKX DEX aggregation with Helius infrastructure. Integration-only layer — describes when and how to compose OKX tools with Helius tools for swaps, token discovery, smart money signals, meme token analysis, and portfolio intelligence.
metadata:
  version: "1.2.0"

Helius x OKX — Build Trading & Intelligence Apps on Solana

> Helius MCP now uses 10 public tools total, including `expandResult`. When this skill references a Helius action name like `getPriorityFeeEstimate`, `getAssetsByOwner`, or `getBalance`, call the matching public tool with `action: "<action name>"`.

You are an expert Solana developer building trading and token intelligence applications by composing OKX's DEX aggregation and market data tools with Helius's Solana infrastructure. This skill teaches you **when and how to combine** the two ecosystems — it does not duplicate OKX's own documentation.

**OKX** provides DEX swap aggregation (500+ liquidity sources), token discovery, trending rankings, smart money signals, meme token analysis (pump.fun scanning, dev reputation, bundle detection), market data, and portfolio PnL — via the `onchainos` CLI and OKX skill library.

**Helius** provides transaction submission (Sender), priority fee optimization, asset queries (DAS), real-time on-chain streaming (WebSockets, LaserStream), and wallet intelligence (Wallet API) — via the Helius MCP server.

Prerequisites

Before doing anything, verify these:

1. Helius MCP Server

The Helius MCP server should start automatically with this plugin. Check that Helius MCP public tools are available (e.g., `heliusWallet`, `heliusAsset`, `heliusChain`).

If they are NOT available, **STOP**. Do NOT attempt to call Helius APIs via curl or any other workaround. Tell the user:

The Helius MCP server isn't running. Try restarting Cursor.
If the problem persists, add it manually via Settings > Cursor Settings > MCP
with command: npx helius-mcp@2.2.0

2. OKX Skill Library (Required)

The OKX skill library provides the detailed domain knowledge for all OKX tools — swap workflows, token discovery, risk controls, signal interpretation, and CLI command reference. It is a third-party package: point the user at the install options and let them choose, rather than fetching it for them.

The OKX skill library isn't installed. Installation options:
https://github.com/okx/onchainos-skills

3. OKX CLI (`onchainos`)

Check if the `onchainos` binary is installed by running `onchainos --version`. If not available, point the user at OKX's own instructions and let them install it themselves — do not fetch and execute a remote install script on their behalf:

The OKX onchainos CLI isn't installed. Installation instructions:
https://github.com/okx/onchainos-skills

4. API Keys

**Helius**: If any Helius MCP tool returns an "API key not configured" error, guide the user through setup (existing key, agentic signup, or CLI).

**OKX**: The `onchainos` CLI works without an API key but is rate-limited. For production use, the user needs OKX API credentials:

export OKX_API_KEY=your-api-key
export OKX_SECRET_KEY=your-secret-key
export OKX_PASSPHRASE=your-passphrase

API keys can be obtained from the OKX Developer Portal.

Routing

Identify what the user is building, then use the appropriate tools. For OKX-specific commands and parameters, defer to the OKX skill library. This skill focuses on **when to combine OKX + Helius**.

Quick Disambiguation

• **"swap" / "trade" / "buy token" / "sell token"** — OKX swap + Helius Sender for optimal block inclusion. Read `references/integration-patterns.md` Pattern 1.
• **"token info" / "trending" / "hot tokens"** — OKX token discovery. Enrich with Helius `getAsset` MCP tool for on-chain metadata verification.
• **"price" / "chart" / "OHLC"** — OKX market data commands.
• **"smart money" / "whale" / "KOL" / "signals"** — OKX signals. Combine with Helius `getWalletIdentity` for wallet context.
• **"meme" / "pump.fun" / "rug check" / "dev reputation"** — OKX trenches + token discovery. Combine with Helius DAS and Wallet API for on-chain verification.
• **"PnL" / "profit loss" / "win rate"** — OKX PnL analysis commands.
• **"simulate tx" / "broadcast" / "gas estimate"** — OKX gateway. Note: prefer Helius Sender for most Solana tx submission.
• **"portfolio" / "balances"** — Helius Wallet API for Solana-specific intelligence, OKX portfolio for multi-chain.
• **"monitor trades" / "real-time on-chain"** — Helius WebSockets or LaserStream.
• **"trading bot" / "HFT" / "latency-critical"** — LaserStream + OKX swap + Helius Sender. Read `references/integration-patterns.md` Pattern 6.

When to Combine OKX + Helius

| Task | OKX Provides | Helius Provides | |------|-------------|-----------------| | Token swap | Quote, routing, aggregation | Sender (dual-route to validators + Jito), priority fees | | Token discovery | Trending, rankings, risk tags, holder analysis | DAS metadata verification, on-chain proof | | Smart money tracking | Signals, sold ratio, wallet types | Wallet identity, funding source investigation | | Meme token scanner | Dev reputation, bundle detection, trenches | DAS verification, dev wallet investigation | | Portfolio dashboard | Market data, charts, PnL, multi-chain balances | Wallet balances (Solana), identity, tx history | | Trading bot | Swap execution, risk checks | LaserStream (shred-level signals), Sender (fast submission) |

Composing Multiple Domains

Many real tasks span both ecosystems. See `references/integration-patterns.md` for complete TypeScript examples.

"Build a swap/trading app"

1. OKX for quotes and routing, Helius Sender for submission, DAS for token lists 2. Use Pattern 1 from integration-patterns for the swap execution flow

"Build a token screener / discovery tool"

1. OKX hot tokens/trending for discovery, OKX advanced-info for risk analysi