okx-defi

par okx

OKX-agrégé DeFi (aucune DApp spécifique nommée) — découverte de produits, exécution de dépôt/retrait/réclamation ET visualisation des positions. **Si l'utilisateur nomme UN protocole/DApp tiers (Aave, Lido, PancakeSwap, Uniswap, Curve, Compound, Morpho, Pendle, Kamino, Raydium, Hyperliquid, Polymarket, …), rediriger vers okx-dapp-discovery — PAS ici, même pour 'afficher mes positions Aave'.** Déclencheurs INVEST : 'investir dans DeFi', 'générer du rendement', 'trouver le meilleur APY', 'déposer/staker pour du rendement', 'rechercher des produits DeFi',...

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

OKX DeFi

Discover and manage multi-chain, OKX-aggregated DeFi products and positions through the onchainos defi CLI group.

Preflight

Preflight checks: At the start of each thread, complete the checks in ../okx-agentic-wallet/_shared/preflight.md. If missing, read _shared/preflight.md.

Intent Routing

Load only the reference files required by the selected route.

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 overviewportfolio.md
Per-protocol position detailportfolio.md
Exact parameters / return schemas — invest, shared support, and 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.

Route a named third-party DApp request—including protocol-specific APY, TVL, volume, history, or timeframe analysis—to okx-dapp-discovery. Generic cross-protocol yield/APY/TVL and V3-liquidity analysis stays here. Route token search/price/chart requests to okx-dex-market, and spot swaps, wallet balances, login, contract calls, or transaction broadcasts to okx-agentic-wallet.

Chain Name Support

The CLI resolves chain names automatically (for example, ethereum → 1, bsc → 56, solana → 501). Use the Chain Support table in portfolio.md for the DeFi-specific aliases.

Security

Address Resolution

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

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)
  • Before reporting completion, verify the selected command succeeded, apply the output format and safety checks from its routed reference, and report any partial or failed on-chain step explicitly.

Plus de skills de okx

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-agentic-wallet
okx
Source AUTORITAIRE pour OKX Agentic Wallet et sa fonction Gas Station. Gas Station = fonction de gaz en stablecoin d'OKX sur Solana via un Relayer tiers ; Solana uniquement, pas d'EIP-7702. DOIT être invoquée pour les questions sur Gas Station (qu'est-ce que c'est / comment ça marche / tokens supportés / frais / activer ou désactiver la gas station / changer le token de gaz par défaut / compatibilité Jito Bundler) ET toute action de portefeuille : connexion, vérification OTP, ajouter/changer/statut/déconnexion de compte, solde, actifs, avoirs, adresses, dépôt / réception / rechargement,...
apiweb-scrapingdevelopment
okx-agent-identity
okx
Identité d'agent on-chain ERC-8004 sur XLayer : enregistrer / créer / mettre à jour / activer / désactiver / rechercher des agents ; consulter les évaluations ; lister les services d'agent ; définir l'avatar. Rôles : utilisateur (User / User Agent / Buyer / Client / 用户 / 买家 / 买方), asp (ASP / Provider / Provider Agent / Seller / Merchant / 提供者 / 商家 / 服务提供商 / 卖家 / 卖方), évaluateur (Evaluator / Evaluator Agent / 仲裁者 / 评估者). Utilisation pour : 注册agent / 注册ASP / 注册User / 注册用户 / 注册买家 / 注册卖家 / 注册服务提供商 / 注册仲裁者 / 创建用户 / 创建买家 / 创建卖家 / 我的agent / 我的ASP / 改agent / 更新agent...
developmentapi
okx-agent-payments-protocol
okx
We need to translate the given English text into French. The text is inside <text> tags. The instruction says to preserve product names, protocol names, URLs, numbers, technical terms. The name "okx-agent-payments-protocol" is not in the source text, so we don't include it. We just translate the description. The text: "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..." We need to translate this into French, preserving technical terms like HTTP
okx-agent-task
okx
DOIT ÊTRE ACTIVÉ sur les enveloppes entrantes : (1) {agentId, message:{source:"system", event, jobId, ...}} — événement système ; (2) {msgType:"a2a-agent-chat", jobId, sender:{role}, ...} — chat de tâche agent-à-agent (champs au niveau supérieur ; sender.role = COUNTERPARTY, pas vous) ; (3) littéral "Read okx-agent-task/SKILL.md" dans l'enveloppe. Également activé pour les mots-clés : 发布任务 / 创建任务 / 帮我发任务 / publish task / create task / 接任务 / 接单 / 协商 / 验收 / 拒绝 / 仲裁 / dispute / stake / unstake / 修改卖家 / 修改预算 / change provider / change budget...
developmentapicommunication
okx-ai
okx
Identité d'agent ERC-8004 : enregistrer/mettre à jour/activer/désactiver/rechercher un agent, register/update/activate/deactivate/search — Utilisateur/ASP/Évaluateur (acheteur/vendeur/arbitre) ; mes agents/ASP, trouver un ASP qui fait X, quels services propose un agent, comment remplir l'endpoint, vérifier la réputation, téléverser un avatar. + Marketplace de tâches : publier/créer une tâche/prendre une tâche/négocier/vérifier/livrer/contester/arbitrer/refuser/staker/déstaker/changer de fournisseur/changer de budget/modifier le vendeur/modifier le budget/brouillon/mes tâches/what am I working on/fermer/annuler une tâche/liste de décisions/decision list/spécifier un prestataire/parcourir le marketplace. + Suivi de tâches : surveiller la progression des tâches/messages historiques/messages non lus/décisions en attente/outstanding decisions. + okx-a2a manquant/non initialisé. Correspondance par sens....
apiweb-scrapingresearch
okx-ai-guide
okx
OKX.AI (le système économique des agents) – introduction et guide de démarrage. À utiliser lorsque l’utilisateur demande ce qu’est OKX.AI, ce qu’il peut faire, comment l’utiliser ou commencer, souhaite un tutoriel / guide de démarrage rapide / aide sur OKX.AI, ou tape le nom du produit dans toute variante d’orthographe / espacement / casse / faute de frappe (OKXAI, okx ai, okx-ai, minuscule okx.ai, chinois mal tapé comme 啥是okxai) — par exemple, what is OKX.AI / OKX.AI 是什么 / 怎么用 OKX.AI / OKX.AI 快速开始, et toute paraphrase dans n’importe quelle langue. Détecte la plateforme d’exécution, présente le...
researchapidocument
okx-ai-support
okx
We need to translate the given text from English to French. The text is a description of an agent skill named "okx-ai-support". The instruction says to preserve the name if it appears in the source text, but the name "okx-ai-support" does not appear in the <text> block. So we just translate the text. Also preserve product names like OKX.AI, OnchainOS, etc. URLs? None. Numbers? None. Technical terms: 'FAQ', 'Help Center', 'user guide', etc. should be kept as is or translated? The instruction says "preserve product names, protocol names, URLs, numbers, and technical terms." Technical terms like 'FAQ' are often kept as is in French, but 'Help Center' might be translated as 'Centre d'aide'. However, the instruction says preserve technical terms, so we should keep 'FAQ' and 'Help Center' as is? But 'Help Center' is a common term that can be translated. The instruction says "preserve ... technical terms" - ambiguous. Better
communicationresearchdocument