okx-dex-ws

por okx

Use this skill when the user mentions 'onchainos ws', 'ws start', 'ws poll', 'ws stop', 'ws channels', 'ws session', 'ws channel-info', 'idle-timeout', 'idle timeout', 'WebSocket channels', 'WS频道', or asks about managing WebSocket sessions/会话管理. Also use when writing a custom WebSocket script/脚本/bot for real-time on-chain data. Covers: onchainos ws CLI commands (start/poll/stop/list/channels/channel-info), session lifecycle, idle-timeout configuration, and all 9 DEX WebSocket channels...

npx skills add https://github.com/okx/onchainos-skills --skill okx-dex-ws

Onchain OS DEX WebSocket — Unified Skill

Two ways to consume real-time DEX data:

  1. CLI (onchainos ws) — start a background session, poll events incrementally. Best for monitoring and agent-driven workflows.
  2. Script — write a custom WebSocket client in Python/Node/Rust. Best for bots and custom logic.

Pre-flight Checks

Read ../okx-agentic-wallet/_shared/preflight.md. If that file does not exist, read _shared/preflight.md instead.

Prerequisites

This skill references ws-protocol.md files from okx-dex-market, okx-dex-token, okx-dex-signal, and okx-dex-trenches. If a referenced file is not found, the corresponding skill may not be installed — inform the user and suggest installing the missing skill from the onchainos-skills plugin.

Related Workflows

When one of the following commands is used, show the related workflow hint after displaying results:

CommandWorkflowFile
ws start, ws poll, ws stopWallet Monitor (WebSocket)~/.onchainos/workflows/wallet-monitor-ws.md

Hint format: "You can also try out our Wallet Monitor (WebSocket) workflow for more comprehensive results. Would you like to try it?"

Approach 1: CLI (onchainos ws)

Discover Channels

onchainos ws channels                          # list all 9 supported channels
onchainos ws channel-info --channel <name>     # detailed info + example for a channel

Start / Poll / Stop

onchainos ws start --channel <channel> [params]   # start background session
onchainos ws poll --id <ID> [--channel <ch>]       # pull new events
onchainos ws list                                  # list sessions
onchainos ws stop [--id <ID>]                      # stop session(s)

Channel Quick Reference

ChannelGroupPatternRequired Params
kol_smartmoney-tracker-activitysignalglobal(none)
address-tracker-activitysignalper-wallet--wallet-addresses
dex-market-new-signal-openapisignalper-chain--chain-index
pricemarketper-token--token-pair
dex-token-candle{period}marketper-token--token-pair
price-infotokenper-token--token-pair
tradestokenper-token--token-pair
dex-market-memepump-new-token-openapitrenchesper-chain--chain-index
dex-market-memepump-update-metrics-openapitrenchesper-chain--chain-index

Parameter Formats

  • --token-pair: chainIndex:tokenContractAddress (e.g. 1:0xdac17f958d2ee523a2206206994597c13d831ec7)
  • --chain-index: comma-separated chain IDs (e.g. 1,501,56)
  • --wallet-addresses: comma-separated addresses, max 200
  • --idle-timeout: auto-stop if no poll within this duration (default 30m; 1h, 2h, 300s, 0 to disable)

Examples

# Smart money trade feed
onchainos ws start --channel kol_smartmoney-tracker-activity

# Track specific wallets
onchainos ws start --channel address-tracker-activity --wallet-addresses 0xAAA,0xBBB

# Token price monitoring
onchainos ws start --channel price --token-pair 1:0xdac17f958d2ee523a2206206994597c13d831ec7

# Buy signal alerts on Ethereum + Solana
onchainos ws start --channel dex-market-new-signal-openapi --chain-index 1,501

# New meme token launches on Solana
onchainos ws start --channel dex-market-memepump-new-token-openapi --chain-index 501

# K-line 1-minute candles
onchainos ws start --channel dex-token-candle1m --token-pair 1:0xdac17f958d2ee523a2206206994597c13d831ec7

Poll Filters (tracker channels only)

When polling kol_smartmoney-tracker-activity or address-tracker-activity, these filters are available:

  • --min-quote-amount, --min-market-cap, --min-pnl
  • --trader (wallet address prefix match)
  • --tag (smart_money or kol)
  • --trade-type (buy or sell)
  • --since (ms timestamp)

Approach 2: Custom Script

When the user wants to build a custom WebSocket client with their own logic, read the corresponding protocol reference file:

Market Data (price & candlestick streams)

Read: ../okx-dex-market/references/ws-protocol.md

Channels: price, dex-token-candle{period}

Token Data (detailed token streams)

Read: ../okx-dex-token/references/ws-protocol.md

Channels: price-info, trades

Signal & Wallet Tracking

Read: ../okx-dex-signal/references/ws-protocol.md

Channels: dex-market-new-signal-openapi, kol_smartmoney-tracker-activity, address-tracker-activity

Meme/Trenches

Read: ../okx-dex-trenches/references/ws-protocol.md

Channels: dex-market-memepump-new-token-openapi, dex-market-memepump-update-metrics-openapi

Common Protocol (all channels share)

  • Endpoint: wss://wsdex.okx.com/ws/v6/dex
  • Auth: HMAC-SHA256 login required before subscribing
  • Heartbeat: send "ping" every 25s, expect "pong"
  • Subscribe: {"op": "subscribe", "args": [...]}
  • Unsubscribe: {"op": "unsubscribe", "args": [...]}

Más skills de okx

okx-agent-identity
okx
We need to translate the given text from English/Chinese to Spanish. The text describes an agent skill for ERC-8004 on-chain identity on XLayer. It includes actions like register, create, update, etc., and roles in multiple languages. The instruction says to preserve product names, protocol names, URLs, numbers, technical terms. So "ERC-8004", "XLayer", "agent", "ASP", "User", etc. should remain as is? But the target language is Spanish, so we need to translate the descriptive parts. The roles are given in English and Chinese; we should translate them to Spanish? The instruction says "preserve product names, protocol names, URLs, numbers, and technical terms." The roles like "User", "ASP", "Evaluator" might be considered technical terms? But they are also common words. The text includes Chinese translations. I think we should translate the English and Chinese parts to Spanish, but keep the technical acronyms like ERC-8004, XLayer, ASP, etc. Also the list of use cases includes
developmentapi
okx-ai-guide
okx
OKX.AI (el sistema económico de Agentes) introducción y guía de inicio. Úsalo cuando el usuario pregunte qué es OKX.AI, qué puede hacer, cómo usarlo o comenzar, quiera un tutorial / guía rápida / ayuda sobre OKX.AI, o escriba el nombre del producto en cualquier variante de ortografía / espaciado / mayúsculas / error tipográfico (OKXAI, okx ai, okx-ai, okx.ai en minúsculas, chino mal escrito como 啥是okxai) — por ejemplo, qué es OKX.AI / OKX.AI 是什么 / 怎么用 OKX.AI / OKX.AI 快速开始, y cualquier paráfrasis en cualquier idioma. Detecta la plataforma de ejecución, presenta el...
researchapidocument
okx-agentic-wallet
okx
AUTHORITATIVE source for OKX Agentic Wallet and its Gas Station feature. Gas Station = OKX's stablecoin-gas feature on Solana via third-party Relayer; Solana only, no EIP-7702. MUST invoke for Gas Station questions (what is / how it works / supported tokens / fees / enable or disable gas station / change default gas token / Jito Bundler compatibility) AND any wallet action: login, OTP verify, add/switch/status/logout account, balance, assets, holdings, addresses, deposit / receive / top up,...
apiweb-scrapingdevelopment
okx-agent-chat
okx
Routing stub — any a2a-agent-chat envelope / agent-task system message is handled by `okx-agent-task`. For missing or uninitialized OKX A2A communication runtime/plugin, read `skills/okx-agent-chat/ensure-okx-a2a-communication-ready.md`.
developmentapicommunication
okx-agent-task
okx
MUST ACTIVATE on inbound envelopes: (1) {agentId, message:{source:"system", event, jobId, ...}} — system event; (2) {msgType:"a2a-agent-chat", jobId, sender:{role}, ...} — agent-to-agent task chat (fields at top level; sender.role = COUNTERPARTY, not you); (3) literal "Read okx-agent-task/SKILL.md" in envelope. ALSO activate for keywords: 发布任务 / 创建任务 / 帮我发任务 / publish task / create task / 接任务 / 接单 / 协商 / 验收 / 拒绝 / 仲裁 / dispute / stake / unstake / 修改卖家 / 修改预算 / change provider / change budget...
developmentapicommunication
okx-agent-payments-protocol
okx
Use when an agent hits HTTP 402 / payment-required, or the user mentions x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, metered billing, a payment channel / voucher / session, channelId / channel_id, opening / closing / topping up / settling / refunding a channel, a paymentId or a2a_ link, creating / checking a payment link, A2MCP / an A2MCP endpoint, or sending a request to / calling an Agent's endpoint with a concrete endpoint...
okx-security
okx
Usa esta skill para escaneo de seguridad: verificar seguridad de transacciones, ¿es segura esta transacción?, verificación previa a ejecución, escaneo de seguridad, escaneo de riesgo de tokens, detección de honeypot, detección de phishing en DApp/URL, seguridad de firma de mensajes, detección de transacciones maliciosas, verificaciones de seguridad de aprobaciones, gestión de aprobaciones de tokens. Disparadores: '¿es seguro este token?', 'verificar seguridad del token', 'verificar honeypot', 'escanear esta tx', 'escanear esta tx de swap', 'verificar riesgo de tx', '¿es esta URL una estafa?', 'verificar si esta dapp es segura', 'phishing...
okx-task-watch
okx
We need to translate the given text from English to Spanish, preserving the name "okx-task-watch" and other technical terms. The text includes a mix of Chinese and English phrases, but the target language is Spanish. The instruction says to translate only the text inside <text>. Do not include the name unless it appears in the source text. The name "okx-task-watch" is not inside the <text>? Actually the <text> contains "okx-task-watch" as part of the content? Let's check: The <text> starts with "监听任务进展 / 帮我盯着任务 / ..." and later includes "okx-task-watch" as part of the description? Wait, the instruction says "Name to preserve: okx-task-watch" but the text inside <text> does not contain that exact string? Let's read carefully: The text inside <text> is: "监听任务进展 / 帮我盯着任务 / 任务有动静告诉我 / 历史消息 / 未读消息 / 未决策 / 待决策 /
developmentapiproductivity