Okx Agentic Wallet
Wire an OKX OnchainOS agentic wallet into your product so agents resolve chain names, create addresses on seven core chains, and use Gas Station stablecoins on eleven EVM networks.
Overview
OKX Agentic Wallet is an agent skill for the Build phase that documents OKX OnchainOS wallet chains, address creation support, and Gas Station stablecoin rules for agentic wallet integrations.
Install
npx skills add https://github.com/okx/onchainos-skills --skill okx-agentic-walletWhat is this skill?
- Human-readable chain aliases resolve to chainIndex for CLI and agent calls
- Wallet address creation documented for 7 chains including Ethereum, Base, Solana, BSC, Arbitrum, and XLayer
- Gas Station matrix covers 11 EVM chains with native symbols and USDT/USDC/USDG acceptance
- Broader wallet interaction supports 17+ chains via `onchainos wallet chains` beyond the seven create-address chains
- 7 chains support wallet address creation
- 11 EVM chains in Gas Station matrix
- 17+ chains for wallet interaction via onchainos wallet chains
Adoption & trust: 4.8k installs on skills.sh; 284 GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your agent keeps confusing chain names, chainIndex values, and which stablecoins fund gas on each EVM network when integrating OKX wallets.
Who is it for?
Builders adding OKX OnchainOS wallet commands to agents or backends on Ethereum, L2s, and Solana-aligned products.
Skip if: Non-crypto apps, wallet integrations without OKX OnchainOS, or production treasury moves without human review of keys and balances.
When should I use this skill?
Implementing OKX OnchainOS wallet flows, resolving chain names to chainIndex, or configuring Gas Station payments per chain.
What do I get? / Deliverables
Integrations use the documented seven-chain address matrix and eleven-chain Gas Station table so CLI and agent commands target the correct network and payment token.
- Correct chainIndex and alias mappings in code or config
- Gas Station token eligibility per chain documented in integration
- Wallet create-address scope limited to supported seven chains
Recommended Skills
Journey fit
Wallet and chain integration work happens while building agent or backend features that talk to on-chain infrastructure. Integrations subphase captures CLI/API wiring to external wallet and gas services rather than smart-contract authoring alone.
How it compares
Reference integration knowledge for OKX OnchainOS—not a generic MetaMask or ethers.js tutorial skill.
Common Questions / FAQ
Who is okx-agentic-wallet for?
Solo developers building agentic crypto products who standardize on OKX OnchainOS CLI patterns for wallets and gas funding.
When should I use okx-agentic-wallet?
During Build integrations when mapping chain aliases, enabling wallet address creation on supported chains, or configuring Gas Station stablecoin payments before Ship security review.
Is okx-agentic-wallet safe to install?
Wallet skills can imply network access and sensitive operations; review the Security Audits panel on this page and never let an agent move mainnet funds without explicit safeguards.
SKILL.md
READMESKILL.md - Okx Agentic Wallet
# Shared Chain Name Support > This file is shared across all onchainos skills. The CLI accepts human-readable chain names and resolves them automatically. ## Wallet address creation (7 chains) The following 7 chains support **wallet address creation** (i.e., you can generate a wallet address on these chains): | Chain | Name | chainIndex | |---|---|---| | XLayer | `xlayer` | `196` | | XLayer Testnet | `xlayer_test` | `1952` | | Solana | `solana` | `501` | | Ethereum | `ethereum` | `1` | | Base | `base` | `8453` | | BSC | `bsc` | `56` | | Arbitrum | `arbitrum` | `42161` | > **Note**: The wallet supports interacting with 17+ chains beyond this list (e.g., Polygon, Avalanche, Optimism). > Run `onchainos wallet chains` for the full list of supported chains. ## Gas Station supported chains and tokens (11 EVM chains) Authoritative matrix for Gas Station. Use this when the Agent needs chain display names, native token symbols, or the set of stablecoins accepted on each chain. | chainIndex | Display name | Native symbol | USDT | USDC | USDG | |---|---|---|---|---|---| | `1` | Ethereum | ETH | ✓ | ✓ | ✓ | | `56` | BNB Chain | BNB | ✓ | ✓ | | | `8453` | Base | ETH | ✓ | ✓ | | | `42161` | Arbitrum One | ETH | ✓ | ✓ | | | `137` | Polygon | MATIC | ✓ | ✓ | | | `10` | Optimism | ETH | ✓ | ✓ | | | `1030` | Conflux eSpace | CFX | ✓ | ✓ | | | `59144` | Linea | ETH | ✓ | ✓ | | | `534352` | Scroll | ETH | ✓ | ✓ | | | `10143` | Monad | MON | ✓ | ✓ | | | `146` | Sonic EVM | S | | ✓ | | > **Always derive the per-tx token set from the Phase 1 response's `gasStationTokenList`** — it's backend-authoritative and already scoped to the current chain. The table above is for reference only (FAQ answers, chain-list questions, unsupported-chain detection). chainIndex values for Conflux / Monad / Sonic are included for completeness; verify against `onchainos wallet chains` before relying on them for dispatch. **Related rules** (see `references/gas-station.md`): - Gas Station only triggers on the 11 chains above; for any other chain the backend returns `gasStationUsed=false` and the default native-gas flow runs. - Per-chain setup is one-time and happens automatically inside the first Gas Station transaction on that chain. - Every Gas Station state (enable flag, default gas token) is scoped to `(account, chain)` — switching a chain doesn't affect others. # Shared Pre-flight Checks > This file is shared across all onchainos skills. Follow these steps before the first `onchainos` command each session. Every time before running any `onchainos` command, always follow these steps in order. Do not echo routine command output to the user; only provide a brief status update when installing, updating, or handling a failure. 1. **Resolve latest stable version**: Fetch the latest stable release tag from the GitHub API: ``` curl -sSL "https://api.github.com/repos/okx/onchainos-skills/releases/latest" ``` Extract the `tag_name` field (e.g., `v1.0.5`) into `LATEST_TAG`. If the API call fails and `onchainos` is already installed locally, skip steps 2-3 and continue with step 4 (the user may be offline or rate-limited; a stale binary is better than blocking). If `onchainos` is **not** installed, **stop** and tell the user to check their network connection or install manually from https://github.com/okx/onchainos-skills. 2. **Install or update**: If `onchainos` is not found, or if the cache at `~/.onchainos/last_check` (`$env:USERPROFILE\.onchainos\last_check` on Windows) is older than 12 hours: - Download the installer and its checksum file from the latest release tag: - **macOS/Linux**: `curl -sSL "https://raw.githubusercontent.com/okx/onchainos-skills/${LATEST_TAG}/install.sh" -o /tmp/onchainos-install.sh` `curl -sSL "https://github.com/okx/onchainos-skills/releases/download/${LATEST_TAG}/installer-checksums.txt" -o /tmp/installer-checksums.txt` - **Windows**: `Invoke-WebRequest -Uri "https://raw.gi