okx-defi

tarafından okx

OKX tarafından toplanan DeFi (belirli bir DApp adı verilmemiş) — ürün keşfi, para yatırma/çekme/talep etme işlemleri VE pozisyon görüntüleme. **Kullanıcı herhangi bir üçüncü taraf protokol/DApp adı verirse (Aave, Lido, PancakeSwap, Uniswap, Curve, Compound, Morpho, Pendle, Kamino, Raydium, Hyperliquid, Polymarket, …), okx-dapp-discovery'ye yönlendirin — buraya değil, 'Aave pozisyonlarımı göster' için bile.** YATIRIM tetikleyicileri: 'DeFi'ye yatırım yap', 'getiri kazan', 'en iyi APY'yi bul', 'getiri için para yatır/stake et', 'DeFi ürünlerini ara',...

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.

okx tarafından daha fazla skill

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
OKX Agentic Wallet ve Gas Station özelliği için YETKİLİ kaynak. Gas Station = OKX'in Solana üzerinde üçüncü taraf Relayer aracılığıyla stablecoin-gas özelliği; yalnızca Solana, EIP-7702 yok. Gas Station soruları (nedir / nasıl çalışır / desteklenen token'lar / ücretler / gas station'ı etkinleştirme veya devre dışı bırakma / varsayılan gas token'ını değiştirme / Jito Bundler uyumluluğu) VE herhangi bir cüzdan işlemi için çağrılmalıdır: giriş, OTP doğrulama, hesap ekleme/değiştirme/durum/çıkış, bakiye, varlıklar, portföy, adresler, para yatırma/al
apiweb-scrapingdevelopment
okx-agent-identity
okx
We need to translate the given text from English/Chinese to Turkish. The text describes an agent skill for ERC-8004 on-chain Agent 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", "evaluator" etc. should remain as is or translated? The instruction says "preserve product names, protocol names, URLs, numbers, and technical terms." So "ERC-8004" and "XLayer" are protocol/product names, keep them. "Agent" might be a technical term, but it's also a common word. However, in context, it's part of the skill name "okx-agent-identity" which is preserved but not in the text. The text uses "agent" repeatedly. Should we translate "agent" to Turkish? The instruction says "preserve technical terms". "Agent" is a technical term in
developmentapi
okx-agent-payments-protocol
okx
Bir aracı HTTP 402 / payment-required hatası aldığında veya kullanıcı x402, x402Version, X-PAYMENT, PAYMENT-REQUIRED, PAYMENT-SIGNATURE, WWW-Authenticate: Payment, permit2, upto, metered billing, bir ödeme kanalı / kupon / oturum, channelId / channel_id, bir kanalı açma / kapatma / doldurma / kapatma / ger
okx-agent-task
okx
Gelen zarflarda ZORUNLU etkinleştirme: (1) {agentId, message:{source:"system", event, jobId, ...}} — sistem olayı; (2) {msgType:"a2a-agent-chat", jobId, sender:{role}, ...} — ajanlar arası görev sohbeti (alanlar üst düzeyde; sender.role = KARŞI TARAF, siz değil); (3) zarfta "Read okx-agent-task/SKILL.md" ifadesi. AYRICA şu anahtar kelimeler için etkinleştir: 发布任务 / 创建任务 / 帮我发任务 / publish task / create task / 接任务 / 接单 / 协商 / 验收 / 拒绝 / 仲裁 / dispute / stake / unstake / 修改卖家 / 修改预算 / change provider / change budget...
developmentapicommunication
okx-ai
okx
ERC-8004 Agent kimliği: agent kaydet/güncelle/listele/listeden kaldır/ara, register/update/activate/deactivate/search — Kullanıcı/ASP/Değerlendirici (alıcı/satıcı/arabulucu); benim agent/ASP’lerim, X yapan ASP/agent bul, hangi hizmetler var/endpoint nasıl doldurulur/itibarı kontrol et/avatar yükle. + Görev Pazarı: yayınla/görev oluştur/teklif al/müzakere et/kabul et/deliver/anlaşmazlık/arabuluculuk/reddet/stake/unstake/sağlayıcıyı değiştir/bütçeyi değiştir/satıcıyı değiştir/bütçeyi değiştir/draft/taslak/görevlerim/my tasks/ne üzerinde çalışıyorum/kapat/görevi iptal et/karar listesi/decision list/belirlenmiş hizmet sağlayıcı/pazarı keşfet. + görev izleme: görev ilerlemesini dinle/geçmiş mesajlar/okunmamış mesajlar/karar verilmemiş/outstanding decisions. + okx-a2a eksik/başlatılmamış. Anlama göre eşleştir....
apiweb-scrapingresearch
okx-ai-guide
okx
OKX.AI (Ajan ekonomik sistemi) tanıtımı ve kullanıma başlama girişi. Kullanıcı OKX.AI’nin ne olduğunu, ne yapabileceğini, nasıl kullanılacağını veya nasıl başlanacağını sorduğunda, OKX.AI eğitimi / hızlı başlangıç / yardım istediğinde veya ürün adını herhangi bir yazım / boşluk / büyük-küçük harf / yazım hatası varyantında (OKXAI, okx ai, okx-ai, küçük harfli okx.ai, yanlış yazılmış Çince 啥是okxai) yazdığında — örn. OKX.AI nedir / OKX.AI 是什么 / 怎么用 OKX.AI / OKX.A
researchapidocument
okx-ai-support
okx
We need to translate the given text from English to Turkish. The text is a description of an agent skill named "okx-ai-support". The instruction says to preserve product names, protocol names, URLs, numbers, technical terms. Also do not include the name unless it appears in source text. The name "okx-ai-support" does not appear in the source text, so we don't include it. The source text includes "OKX.AI", "OKX AI support", "OnchainOS support" - these should be preserved as proper nouns. Also "FAQ" is an acronym, preserve. "Help Center" might be translated? But it's a proper name? The instruction says preserve product names, so "OKX.AI" and "OnchainOS" are product names. "Help Center" could be considered a common term but it's part of the service name? I'll keep it as "Help Center" or translate? The instruction says "preserve product names, protocol names, URLs, numbers, and technical terms." "Help Center" is
communicationresearchdocument