ideabrowser.com — find trending startup ideas with real demand
Try itnpx skills add https://github.com/okx/onchainos-skills --skill okx-dex-trenches7 commands for meme token discovery, developer analysis, bundle detection, and co-investor tracking.
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.
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 proceed to run the command (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.
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:
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.txtInvoke-WebRequest -Uri "https://raw.githubusercontent.com/okx/onchainos-skills/${LATEST_TAG}/install.ps1" -OutFile "$env:TEMP\onchainos-install.ps1"
Invoke-WebRequest -Uri "https://github.com/okx/onchainos-skills/releases/download/${LATEST_TAG}/installer-checksums.txt" -OutFile "$env:TEMP\installer-checksums.txt"installer-checksums.txt. On mismatch, stop and warn — the installer may have been tampered with.sh /tmp/onchainos-install.sh (or & "$env:TEMP\onchainos-install.ps1" on Windows).
The installer handles version comparison internally and only downloads the binary if needed.Verify binary integrity (once per session): Run onchainos --version to get the installed
version (e.g., 1.0.5 or 2.0.0-beta.0). Construct the installed tag as v<version>.
Download checksums.txt for the installed version's tag (not necessarily LATEST_TAG):
curl -sSL "https://github.com/okx/onchainos-skills/releases/download/v<version>/checksums.txt" -o /tmp/onchainos-checksums.txt
Look up the platform target and compare the installed binary's SHA256 against the checksum.
On mismatch, reinstall (step 2) and re-verify. If still mismatched, stop and warn.
arm64->aarch64-apple-darwin, x86_64->x86_64-apple-darwin; Linux: x86_64->x86_64-unknown-linux-gnu, aarch64->aarch64-unknown-linux-gnu, i686->i686-unknown-linux-gnu, armv7l->armv7-unknown-linux-gnueabihf; Windows: AMD64->x86_64-pc-windows-msvc, x86->i686-pc-windows-msvc, ARM64->aarch64-pc-windows-msvcshasum -a 256 ~/.local/bin/onchainos; Windows: (Get-FileHash "$env:USERPROFILE\.local\bin\onchainos.exe" -Algorithm SHA256).Hash.ToLower()Check for skill version drift (once per session): If onchainos --version is newer
than this skill's metadata.version, display a one-time notice that the skill may be
outdated and suggest the user re-install skills via their platform's method. Do not block.
Do NOT auto-reinstall on command failures. Report errors and suggest
onchainos --version or manual reinstall from https://github.com/okx/onchainos-skills.
Rate limit errors. If a command hits rate limits, the shared API key may
be throttled. Suggest creating a personal key at the
OKX Developer Portal. If the
user creates a .env file, remind them to add .env to .gitignore.
okx-dex-signalokx-dex-signalokx-dex-tokenokx-dex-tokenokx-dex-tokenokx-dex-marketokx-dex-marketokx-dex-swapokx-wallet-portfolio| Chinese | English / Platform Terms | Maps To |
|---|---|---|
| 扫链 | trenches, memerush, 战壕, 打狗 | onchainos memepump tokens |
| 同车 | aped, same-car, co-invested | onchainos memepump aped-wallet |
| 开发者信息 | dev info, developer reputation, rug check | onchainos memepump token-dev-info |
| 捆绑/狙击 | bundler, sniper, bundle analysis | onchainos memepump token-bundle-info |
| 持仓分析 | holding analysis (meme context) | onchainos memepump token-details (tags fields) |
| 社媒筛选 | social filter | onchainos memepump tokens --has-x, --has-telegram, etc. |
| 新盘 / 迁移中 / 已迁移 | NEW / MIGRATING / MIGRATED | onchainos memepump tokens --stage |
| pumpfun / bonkers / bonk / believe / bags / mayhem | protocol names (launch platforms) | onchainos memepump tokens --protocol-id-list <id> |
Protocol names are NOT token names. When a user mentions pumpfun, bonkers, bonk, believe, bags, mayhem, fourmeme, etc., look up their IDs via onchainos memepump chains, then pass to --protocol-id-list. Multiple protocols: comma-separate the IDs.
When presenting memepump-token-details or memepump-token-dev-info responses, translate JSON field names into human-readable language. Never dump raw field names to the user:
top10HoldingsPercent → "top-10 holder concentration"rugPullCount → "rug pull count / 跑路次数"bondingPercent → "bonding curve progress"# Get supported chains and protocols for meme pump
onchainos memepump chains
# List new meme pump tokens on Solana
onchainos memepump tokens --chain solana --stage NEW
# Get meme pump token details
onchainos memepump token-details --address <address> --chain solana
# Check developer reputation for a meme token
onchainos memepump token-dev-info --address <address> --chain solana
# Get bundle/sniper analysis
onchainos memepump token-bundle-info --address <address> --chain solana
# Find similar tokens by same dev
onchainos memepump similar-tokens --address <address> --chain solana
# Get aped (same-car) wallet list
onchainos memepump aped-wallet --address <address> --chain solana
Currently supports: Solana (501), BSC (56), X Layer (196), TRON (195). Always verify with onchainos memepump chains first.
| # | Command | Description |
|---|---|---|
| 1 | onchainos memepump chains | Get supported chains and protocols |
| 2 | onchainos memepump tokens --chain <chain> [--stage <stage>] | List meme pump tokens with advanced filtering (default stage: NEW) |
| 3 | onchainos memepump token-details --address <address> | Get detailed info for a single meme pump token |
| 4 | onchainos memepump token-dev-info --address <address> | Get developer analysis and holding info |
| 5 | onchainos memepump similar-tokens --address <address> | Find similar tokens by same creator |
| 6 | onchainos memepump token-bundle-info --address <address> | Get bundle/sniper analysis |
| 7 | onchainos memepump aped-wallet --address <address> | Get aped (same-car) wallet list |
onchainos memepump chainsonchainos memepump tokensonchainos memepump token-detailsonchainos memepump token-dev-infoonchainos memepump similar-tokensonchainos memepump token-bundle-infoonchainos memepump aped-wallet--chain solana); verify support with onchainos memepump chains first--stage for memepump-tokens → ask user which stage (NEW / MIGRATING / MIGRATED)onchainos memepump chains to get the protocol ID, then pass --protocol-id-list <id> to memepump-tokens. Do NOT use okx-dex-token to search for protocol names as tokens.memepump-token-dev-info, present as a developer reputation reportmemepump-token-details, present as a token safety summary highlighting red/green flagsmemepump-tokens, never merge or deduplicate entries that share the same symbol. Different tokens can have identical symbols but different contract addresses — each is a distinct token and must be shown separately. Always include the contract address to distinguish them.| Just called | Suggest |
|---|---|
memepump-chains | 1. Browse tokens → onchainos memepump tokens (this skill) |
memepump-tokens | 1. Pick a token for details → onchainos memepump token-details (this skill) 2. Check dev → onchainos memepump token-dev-info (this skill) |
memepump-token-details | 1. Dev analysis → onchainos memepump token-dev-info (this skill) 2. Similar tokens → onchainos memepump similar-tokens (this skill) 3. Bundle check → onchainos memepump token-bundle-info (this skill) |
memepump-token-dev-info | 1. Check bundle activity → onchainos memepump token-bundle-info (this skill) 2. View price chart → okx-dex-market (onchainos market kline) |
memepump-similar-tokens | 1. Compare with details → onchainos memepump token-details (this skill) |
memepump-token-bundle-info | 1. Check aped wallets → onchainos memepump aped-wallet (this skill) |
memepump-aped-wallet | 1. Validate token safety (honeypot, holder concentration) → okx-dex-token (onchainos token advanced-info) 2. View price chart → okx-dex-market (onchainos market kline) 3. Buy the token → okx-dex-swap (quote → swap → onchainos wallet contract-call to execute) |
Present conversationally — never expose skill names or endpoint paths to the user.
User: "Show me new meme tokens and check if any look safe"
1. okx-dex-trenches onchainos memepump chains → discover supported chains & protocols
2. okx-dex-trenches onchainos memepump tokens --chain <chain> --stage NEW → browse new tokens
↓ pick an interesting token
3. okx-dex-trenches onchainos memepump token-details --address <address> --chain <chain> → full token detail + audit tags
4. okx-dex-trenches onchainos memepump token-dev-info --address <address> --chain <chain> → check dev reputation (rug pulls, migrations)
5. okx-dex-trenches onchainos memepump token-bundle-info --address <address> --chain <chain> → check for bundlers/snipers
6. okx-dex-market onchainos market kline --address <address> --chain <chain> → view price chart
↓ user decides to buy
7. okx-dex-swap onchainos swap quote --from <native_addr> --to <address> --amount ... --chain <chain>
8. okx-dex-swap onchainos swap swap --from <native_addr> --to <address> --amount ... --chain <chain> --wallet <addr>
↓ get swap calldata, then execute via one of two paths:
Path A (user-provided wallet): user signs externally → onchainos gateway broadcast --signed-tx <tx> --address <addr> --chain <chain>
Path B (Agentic Wallet):
Solana: onchainos wallet contract-call --to <tx.to> --chain sol --unsigned-tx <tx.data>
EVM: onchainos wallet contract-call --to <tx.to> --chain <chain> --value <value_in_UI_units> --input-data <tx.data>
Data handoff: tokenAddress from step 2 is reused as <address> in steps 3–8. The tx.to and tx.data come from the swap swap response. EVM --value needs unit conversion: tx.value / 10^nativeToken.decimal (e.g., wei ÷ 10^18 = ETH). If tx.value is "0" or empty, use "0". EVM non-native tokens also need an approve step before swap (see okx-dex-swap skill).
User: "Check if this meme token is safe before I buy"
1. okx-dex-trenches onchainos memepump token-details --address <address> --chain <chain> → basic info + audit tags
2. okx-dex-trenches onchainos memepump token-dev-info --address <address> --chain <chain> → dev history + holding
3. okx-dex-trenches onchainos memepump similar-tokens --address <address> --chain <chain> → other tokens by same dev
4. okx-dex-trenches onchainos memepump token-bundle-info --address <address> --chain <chain> → bundler analysis
5. okx-dex-trenches onchainos memepump aped-wallet --address <address> --chain <chain> → who else is holding
User: "A whale signal came in — is it a meme/pump.fun token? Check it out"
1. okx-dex-signal onchainos signal list --chain <chain> --wallet-type 3 → identify the signaled token address
↓ token looks like a meme/pump.fun launch
2. okx-dex-trenches onchainos memepump token-details --address <address> --chain <chain> → confirm it's a meme token, check audit tags
3. okx-dex-trenches onchainos memepump token-dev-info --address <address> --chain <chain> → check dev rug pull history
4. okx-dex-trenches onchainos memepump token-bundle-info --address <address> --chain <chain> → verify the whale signal isn't a bundler
↓ checks pass
5. okx-dex-market onchainos market kline --address <address> --chain <chain> → confirm price momentum
↓ user decides to buy
6. okx-dex-swap onchainos swap quote --from <native_addr> --to <address> --amount ... --chain <chain>
7. okx-dex-swap onchainos swap swap --from <native_addr> --to <address> --amount ... --chain <chain> --wallet <addr>
↓ get swap calldata, then execute via one of two paths:
Path A (user-provided wallet): user signs externally → onchainos gateway broadcast --signed-tx <tx> --address <addr> --chain <chain>
Path B (Agentic Wallet):
Solana: onchainos wallet contract-call --to <tx.to> --chain sol --unsigned-tx <tx.data>
EVM: onchainos wallet contract-call --to <tx.to> --chain <chain> --value <value_in_UI_units> --input-data <tx.data>
When to use: when a signal-list result has a token address that matches a known meme launchpad (pump.fun, bonkers, etc.) — cross-validate in memepump before acting on the signal.
For detailed parameter tables, return field schemas, and usage examples, consult:
references/cli-reference.md — Full CLI command reference for memepump commandsonchainos memepump chains firstNEW, MIGRATING, or MIGRATEDmemepump-token-details returns null data if the token doesn't exist in meme pump ranking data — it may be on a standard DEXmemepump-token-dev-info returns devHoldingInfo as null if the creator address is unavailablememepump-similar-tokens may return empty array if no similar tokens are foundmemepump-aped-wallet returns empty array if no co-holders foundWhen a command fails with error code 50125 or 80001, display:
DEX is not available in your region. Please switch to a supported region and try again.
Do not expose raw error codes or internal error messages to the user.