okx-defi

द्वारा okx

OKX-aggregated DeFi (no specific DApp named) — product discovery, deposit/withdraw/claim execution, AND positions viewing. **If the user names ANY third-party protocol/DApp (Aave, Lido, PancakeSwap, Uniswap, Curve, Compound, Morpho, Pendle, Kamino, Raydium, Hyperliquid, Polymarket, …), route to okx-dapp-discovery — NOT here, even for 'show my Aave positions'.** INVEST triggers: 'invest in DeFi', 'earn yield', 'find best APY', 'deposit/stake for yield', 'search DeFi products',...

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

OKX DeFi (experimental merge of okx-defi-invest + okx-defi-portfolio)

Multi-chain, OKX-aggregated DeFi in two capabilities behind one skill. Both wrap the same onchainos defi CLI command group.

Pre-flight Checks

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

Intent Routing

User IntentReference
Discover / search DeFi products, find best APYinvest.md
Product detail (APY, TVL, accepted tokens)invest.md
Deposit / stake / provide liquidityinvest.md
Withdraw / redeem a position (full or partial)invest.md
Claim rewards (platform / investment / V3 fee / bonus / unlocked principal)invest.md
APY history, TVL history, V3 depth / price chartsinvest.md
View DeFi positions / holdings overview (持仓)portfolio.md
Per-protocol position detail (持仓详情)portfolio.md
Exact parameters / return schemas — invest & charts commandsinvest-cli-reference.md
Exact parameters / return schemas — positions commandsportfolio-cli-reference.md
Errors / failed deposits / expired calldatainvest-troubleshooting.md
Errors / empty positions / address-format issuesportfolio-troubleshooting.md

Typical flow spans both: view positions (Portfolio) → redeem or claim (Invest). Read both reference files when the request chains them.

Skill Routing

  • For DApp-named investing/lending/staking/positions ("on Aave", "my Hyperliquid balance") → use okx-dapp-discovery
  • For token price/chart or token search by name/contract → use okx-dex-market
  • For DEX spot swap execution → use okx-agentic-wallet
  • For wallet token balances → use okx-agentic-wallet
  • For broadcasting signed transactions → use okx-agentic-wallet
  • For Agentic Wallet login, balance, contract-call → use okx-agentic-wallet

Chain Support

CLI resolves chain names automatically (e.g. ethereum1, bsc56, solana501). Full alias table: references/portfolio.md §Chain Support.

Step 0: Address Resolution (shared by both capabilities)

When the user does NOT provide a wallet address, resolve it automatically from the Agentic Wallet before running any defi command:

1. onchainos wallet status          → check if logged in, get active account
2. onchainos wallet addresses       → get addresses grouped by chain category:
                                       - XLayer addresses
                                       - EVM addresses (Ethereum, BSC, Polygon, etc.)
                                       - Solana addresses
3. Match address to target chain:
   - EVM chains → use EVM address
   - Solana     → use Solana address
   - XLayer     → use XLayer address

Rules:

  • If the user provides an explicit address, use it directly — skip this step
  • If wallet is not logged in, ask the user to log in first (→ okx-agentic-wallet) or provide an address manually
  • If the user says "check all accounts" or "all wallets", use wallet balance --all to get all account IDs, then wallet switch <id> + wallet addresses for each account
  • Always confirm the resolved address with the user before proceeding if the account has multiple addresses of the same type

Address-Chain Compatibility (shared — CRITICAL)

The --address and chain parameters must be compatible. EVM addresses (0x…) can only query EVM chains; Solana addresses (base58) can only query solana. Never mix them — the API will return error 84019 (Address format error).

  • 0x… address → only pass EVM chains: ethereum,bsc,polygon,arbitrum,base,xlayer,avalanche,optimism,fantom,linea,scroll,zksync
  • base58 address → only pass solana
  • Sui address → only pass sui; Tron address (T…) → only pass tron; TON address → only pass ton
  • If the user wants positions across both EVM and Solana, make two separate calls with the respective addresses

Global Notes

  • The wallet address parameter for ALL defi commands is --address
  • defi positions uses --chains (plural, comma-separated); defi position-detail uses --chain (singular)
  • For CLI parameter details, see references/invest-cli-reference.md (invest & charts) and references/portfolio-cli-reference.md (positions)

okx की और Skills

okx-agent-identity
okx
We need to translate the given text from English to Hindi, preserving the name "okx-agent-identity" if it appears, but it does not appear in the text. The text is a description of an agent skill. We must not add any extra commentary, labels, or formatting. Just translate the text inside <text> to Hindi. The text includes technical terms like ERC-8004, XLayer, agent, ASP, evaluator, etc. We should keep those as is or transliterate if needed. Also includes Chinese characters, which should be preserved as they are? The instruction says preserve product names, protocol names, URLs, numbers, technical terms. Chinese characters are part of the text, likely as alternative terms. We should keep them as is. So we translate the English parts to Hindi, but keep the Chinese characters unchanged. Let's break down the text: "ERC-8004 on-chain Agent identity on XLayer: register / create / update / activate / deactivate / search agents; view ratings; list agent services; set avatar. Roles: user (User
developmentapi
okx-ai-guide
okx
We need to translate the given text from English to Hindi. The text is a description of an agent skill for OKX.AI. We must preserve the product name "okx-ai-guide" as per instruction, but it's not in the text. The text includes "OKX.AI" and various spellings. We need to translate the entire content inside <text> to Hindi, keeping product names, URLs, numbers, technical terms unchanged. Also preserve the examples like "what is OKX.AI" etc. but translate the surrounding words. The instruction says "Do not include the name unless it appears in the source text." The name "okx-ai-guide" does not appear in the source text, so we don't include it. We just translate the text. Let's translate paragraph by paragraph. Source: "OKX.AI (the Agent economic system) intro & onboarding entry. Use whenever the user asks what OKX.AI is, what it can do, how to use or get started with it, wants an OKX.AI tutorial
researchapidocument
okx-agentic-wallet
okx
OKX Agentic Wallet और इसकी Gas Station सुविधा के लिए प्राधिकृत स्रोत। Gas Station = तीसरे पक्ष के Relayer के माध्यम से Solana पर OKX का स्थिर-मुद्रा-गैस फीचर; केवल Solana, कोई EIP-7702 नहीं। Gas Station प्रश्नों (यह क्या है / यह कैसे काम करता है / समर्थित टोकन / शुल्क / गैस स्टेशन सक्षम या अक्षम करें / डिफ़ॉल्ट गैस टोकन बदलें / Jito Bundler संगतता) और किसी भी वॉलेट कार्रवाई: लॉगिन, OTP सत्यापन, खाता जोड़ें/स्विच करें/स्थिति/लॉगआउट
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
We need to translate the given text from English to Hindi. The text is a description of conditions for activating an agent skill. It mentions specific patterns and keywords. We must preserve product names, protocol names, URLs, numbers, technical terms. The name "okx-agent-task" appears in the text, so we preserve it. Also preserve terms like "agentId", "message", "source", "event", "jobId", "msgType", "a2a-agent-chat", "sender", "role", "COUNTERPARTY", "SKILL.md", and the Chinese keywords. The translation should be in Hindi script. We need to translate the entire text inside <text> tags. No extra labels. Just the translation. Let's break it down: "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
developmentapicommunication
okx-agent-payments-protocol
okx
जब कोई एजेंट HTTP 402 / payment-required का सामना करता है, या उपयोगकर्ता x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, मीटर्ड बिलिंग, भुगतान चैनल / वाउचर / सत्र, channelId / channel_id, चैनल खोलना / बंद करना / टॉप अप करना / निपटाना / रिफंड करना, paymentId या a2a_ लिंक, भुगतान लिंक बनाना / जांचना, A2MCP / एक A2MCP एंडपॉइंट, या किसी ठोस एंडपॉइंट के साथ एजेंट के एंड
okx-security
okx
इस कौशल का उपयोग सुरक्षा स्कैनिंग के लिए करें: लेन-देन सुरक्षा जांचें, क्या यह लेन-देन सुरक्षित है, निष्पादन-पूर्व जांच, सुरक्षा स्कैन, टोकन जोखिम स्कैनिंग, हनीपॉट पहचान, DApp/URL फ़िशिंग पहचान, संदेश हस्ताक्षर सुरक्षा, दुर्भावनापूर्ण लेन-देन पहचान, अनुमोदन सुरक्षा जांच, टोकन अनुमोदन प्रबंधन। ट्रिगर: 'क्या यह टोकन सुरक्षित है', 'टोकन सुरक्षा जांचें', 'हनीपॉट जांच', 'इस
okx-task-watch
okx
监听任务进展 / 帮我盯着任务 / 任务有动静告诉我 / 历史消息 / 未读消息 / 未决策 / 待决策 / 继续监听 / task watch / user watch / monitor task progress / catch me up on tasks / outstanding decisions — OKX A2A user-session task-notification monitor: live long-poll via `okx-a2a user watch` (also drains backlog of past/missed/unread events on entry) plus un-replied decision_request lister via `okx-a2a user outdated-list`. Not for wallet / gas / task-list / status queries.
developmentapiproductivity