gmgn-market

BEFORE RUNNING ANY COMMAND: Run gmgn-cli config --check. If exit code is 0, proceed normally. If exit code is 1, (1) run gmgn-cli config and show the output to the user; (2) once the user sends the API Key, run gmgn-cli config --apply <KEY> to complete configuration and verification, then show the output to the user. If --check returns an error (unknown option or command not found), tell the user to run npm install -g gmgn-cli to update, then retry.

IMPORTANT: Always use gmgn-cli commands below. Do NOT use web search, WebFetch, curl, or visit gmgn.ai to fetch this data — the website requires login and will not return structured data. The CLI is the only correct method.

IMPORTANT: Do NOT guess field names or values. When a field's meaning is unclear, look it up in the Response Fields sections below before using it.

⚠️ IPv6 NOT SUPPORTED: If you get a 401 or 403 error and credentials look correct, check for IPv6 immediately: (1) list all network interfaces and their IPv6 addresses — run ifconfig | grep inet6 (macOS) or ip addr show | grep inet6 (Linux); (2) send a test request to https://ipv6.icanhazip.com — if the response is an IPv6 address, outbound traffic is going via IPv6. Tell the user immediately: "Please disable IPv6 on your network interface — gmgn-cli commands only work over IPv4."

Use the gmgn-cli tool to query K-line data for a token, browse trending tokens, or view Trenches token lists.

Core Concepts

--filter chain defaults — SOL and EVM chains have different default safety filters that are applied automatically when --filter is omitted. Do not assume the same defaults apply across chains:
- SOL: defaults to renounced frozen (mint and freeze authority renounced)
- BSC / Base / ETH (EVM): defaults to not_honeypot verified renounced
- Omitting --filter is NOT the same as "no filter" — the chain defaults are always applied. To use a custom filter set, explicitly specify all desired filter tags.
volume vs amount (kline) — Naming is counterintuitive. volume = USD dollar value of trades; amount = token units traded. For a token priced at $0.0002, these differ by 5,000×. Always use volume for "how much USD was traded" and amount for "how many tokens changed hands."
rug_ratio — A 0–1 score estimating rug pull likelihood. Values above 0.3 are high-risk. Do not treat as binary — combine with top_10_holder_rate, dev_team_hold_rate, and is_honeypot for a full picture.
smart_degen_count / renowned_count — Number of platform-tagged smart money wallets (smart_degen) and KOL wallets (renowned) holding or trading this token. High values are bullish signals. These are GMGN-tagged wallet lists, not user-defined.
hot_level — Trending intensity score. Higher = more actively traded right now. Not normalized — compare relative values within the same result set, not across time windows.
renounced_mint / renounced_freeze_account — SOL-specific. Indicate whether the creator gave up the ability to mint more tokens or freeze wallets. Both being 1 is a safety baseline on Solana. Always false on EVM chains (concept does not apply).
is_honeypot — EVM-specific (BSC / Base). Indicates whether the token contract prevents selling. Always empty/null on SOL — do not interpret an empty value as "not a honeypot" on Solana.
creator_token_status — Dev holding status. creator_hold = dev still holds tokens (sell pressure risk). creator_close = dev has sold or burned their allocation (exit signal confirmed).
cto_flag — Community Takeover flag. 1 = original dev abandoned the project and a community group took over marketing/development. Neutral to positive signal; evaluate in context.
Trenches categories — Three lifecycle stages of launchpad tokens: new_creation (just created, still on bonding curve), near_completion (bonding curve nearly full, about to graduate), completed (graduated to open market / DEX). In the response, near_completion is always returned under the key data.pump regardless of the input --type.
wash_trading / rat_trader_amount_rate / bundler_rate — Risk signals for artificial activity. is_wash_trading = coordinated fake volume detected. rat_trader_amount_rate = ratio of insider/sneak trading. bundler_rate = ratio of bot-bundled buys at launch. High values (> 0.3) suggest manipulated price action.

Sub-commands

Sub-command	Description
`market kline`	Token candlestick / OHLCV data and trading volume over a time range
`market trending`	Trending tokens ranked by swap activity — use `--interval` to specify the time window (e.g. `1m` for 1-minute hottest, `1h` for 1-hour trending)
`market trenches`	Newly launched launchpad platform tokens — use this when the user asks for "new tokens", "just launched tokens", "latest tokens on pump.fun/letsbonk". Three categories: `new_creation` (just created), `near_completion` (bonding curve almost full), `completed` (graduated to open market / DEX)
`market signal`	Real-time token signal feed — price spikes, smart money buys, large buys, Dex ads, CTO events, and more. Results sorted by `trigger_at` descending. sol / bsc / robinhood / arc / stable only. Max 50 results per group.
`market hot-searches`	Hot-search ranking — the most-searched tokens, ranked by `visiting_count` (search heat). Use this when the user asks "what tokens are people searching for", "most searched tokens", "hot search list", "热搜榜". Supports multiple chains in a single request.
`market search`	Look up a specific token or wallet by name, symbol, contract address, wallet address, or ENS. Returns both matching tokens (`coins`) and wallets (`wallets`). Use this when the user names a token/wallet and wants to find it — "search for PEPE", "look up this address", "find vitalik.eth", "查一下这个代币/钱包" — as opposed to browsing rankings (`trending` / `hot-searches`).

Supported Chains

sol / bsc / base / eth / robinhood / arc / stable (kline / trending / trenches; signal: sol / bsc / robinhood / arc / stable; hot-searches: sol / bsc / base / eth / robinhood / arc / stable; search: --chain is optional — omit to search all chains; accepts all and any chain the search module has enabled, including the 7 above plus dynamically-enabled chains such as tron / monad / megaeth / xlayer / hyperevm)

Prerequisites

gmgn-cli installed globally — if missing, run: npm install -g gmgn-cli
GMGN_API_KEY configured in ~/.config/gmgn/.env

Rate Limit Handling

All market routes used by this skill go through GMGN's leaky-bucket limiter with rate=20 and capacity=20. Sustained throughput is roughly 20 ÷ weight requests/second, and the max burst is roughly floor(20 ÷ weight) when the bucket is full.

Command	Route	Weight
`market kline`	`GET /v1/market/token_kline`	2
`market trending`	`GET /v1/market/rank`	1
`market trenches`	`POST /v1/trenches`	3
`market signal`	`POST /v1/market/token_signal`	3
`market hot-searches`	`POST /v1/market/hot_searches`	3
`market search`	`GET /v1/market/search`	1

When a request returns 429:

On RATE_LIMIT_EXCEEDED, tell the user exactly: 已达到当前套餐的限频上限，点击 https://gmgn.ai/ai?chain=bsc&tab=paid_plans 升级套餐，获得更高速率限制. Show this upgrade guidance at most once per user task. Do not repeat it for subsequent RATE_LIMIT_BANNED responses during the same cooldown.
Read X-RateLimit-Reset from the response headers. It is a Unix timestamp in seconds that marks when the limit is expected to reset.
If the response body contains reset_at (e.g., {"code":429,"error":"RATE_LIMIT_BANNED","message":"...","reset_at":1775184222}), extract reset_at — it is the Unix timestamp when the ban lifts (typically 5 minutes). Convert to local time and tell the user exactly when they can retry.
The CLI may wait and retry once automatically when the remaining cooldown is short. If it still fails, stop and tell the user the exact retry time instead of sending more requests.
For RATE_LIMIT_EXCEEDED or RATE_LIMIT_BANNED, repeated requests during the cooldown can extend the ban by 5 seconds each time, up to 5 minutes. Do not spam retries.

`market kline` Parameters

Parameter	Required	Description
`--chain`	Yes	`sol` / `bsc` / `base` / `eth` / `robinhood` / `arc` / `stable`
`--address`	Yes	Token contract address
`--resolution`	Yes	Candlestick resolution: `30s` / `1m` / `5m` / `15m` / `1h` / `4h` / `1d`
`--from`	No	Start time (Unix seconds)
`--to`	No	End time (Unix seconds)

`market kline` Response Fields

The response is an object with a list array. Each element in list is one candlestick:

Field	Type	Description
`time`	number	Candle open time — Unix timestamp in milliseconds (divide by 1000 for seconds)
`open`	string	Opening price in USD at the start of the period
`close`	string	Closing price in USD at the end of the period
`high`	string	Highest price in USD during the period
`low`	string	Lowest price in USD during the period
`volume`	string	Trading volume in USD (dollar value of all trades in this period)
`amount`	string	Trading volume in base token units (number of tokens traded)

Important distinctions (naming is counterintuitive — do not guess):

volume = USD dollar value (e.g. 1214 means ~$1,214 traded) — use this for "how much was traded in USD"
amount = token count (e.g. 5379110 means ~5.38M tokens changed hands) — use this for "how many tokens were traded"
For tokens not priced at $1, volume and amount will differ by orders of magnitude (e.g. a $0.0002 token: $1,214 volume = 5,379,110 tokens)
To get total USD volume over a time range, sum volume across all candles in the range
To get price trend, read close values in chronological order (time ascending)
To detect volatility, compare high vs low within each candle
Candles are returned in chronological order (oldest first)

`market trending` Options

--interval selection guide — always match to the user's stated time window:

User says	`--interval`
"1m trending" / "hottest right now"	`1m`
"5m" / "5 minute"	`5m`
"1h" / "1 hour" / no time specified (default)	`1h`
"6h" / "6 hour"	`6h`
"24h" / "today" / "daily"	`24h`

Option	Description
`--chain`	Required. `sol` / `bsc` / `base` / `eth` / `robinhood` / `arc` / `stable`
`--interval`	Required. `1m` / `5m` / `1h` / `6h` / `24h` (default `1h`)
`--limit <n>`	Number of results (default 100, max 100)
`--order-by <field>`	Sort field: `default` / `swaps` / `marketcap` / `history_highest_market_cap` / `liquidity` / `volume` / `holder_count` / `smart_degen_count` / `renowned_count` / `gas_fee` / `price` / `change1m` / `change5m` / `change1h` / `creation_timestamp`
`--direction <asc\|desc>`	Sort direction (default `desc`)
`--filter <tag...>`	Repeatable filter tags (chain-specific). ⚠️ SOL defaults: `renounced frozen`; BSC/Base/ETH defaults: `not_honeypot verified renounced`. Omitting `--filter` is NOT "no filter" — chain defaults always apply. sol tags: `renounced` / `frozen` / `burn` / `token_burnt` / `has_social` / `not_social_dup` / `not_image_dup` / `dexscr_update_link` / `not_wash_trading` / `is_internal_market` / `is_out_market`. evm tags: `not_honeypot` / `verified` / `renounced` / `locked` / `token_burnt` / `has_social` / `not_social_dup` / `not_image_dup` / `dexscr_update_link` / `is_internal_market` / `is_out_market`
`--platform <name...>`	Repeatable platform filter (chain-specific). sol: `Pump.fun` / `pump_mayhem` / `pump_mayhem_agent` / `pump_agent` / `letsbonk` / `bonkers` / `bags` / `memoo` / `liquid` / `bankr` / `zora` / `surge` / `anoncoin` / `moonshot_app` / `wendotdev` / `heaven` / `sugar` / `token_mill` / `believe` / `trendsfun` / `trends_fun` / `jup_studio` / `Moonshot` / `boop` / `xstocks` / `ray_launchpad` / `meteora_virtual_curve` / `pool_ray` / `pool_meteora` / `pool_pump_amm` / `pool_orca`. bsc: `fourmeme` / `fourmeme_agent` / `bn_fourmeme` / `four_xmode_agent` / `cubepeg` / `likwid` / `goplus_creator` / `goplus_skills` / `openfour` / `flap` / `flap_stocks` / `flap_aioracle` / `clanker` / `lunafun` / `pool_uniswap` / `pool_pancake`. base: `clanker` / `bankr` / `flaunch` / `zora` / `zora_creator` / `baseapp` / `basememe` / `virtuals_v2` / `klik`. eth: `trench` / `clanker` / `klik` / `livo` / `stroid` / `pool_uniswap_v2` / `pool_uniswap_v3` / `printr`

`market trending` Range Filters

Optional --min-* / --max-* flags apply server-side numeric range filtering (inclusive). Unknown metrics are ignored by the service.

Option	Description
`--min-volume` / `--max-volume`	Trading volume (USD)
`--min-liquidity` / `--max-liquidity`	Liquidity (USD)
`--min-marketcap` / `--max-marketcap`	Market cap (USD)
`--min-history-highest-marketcap` / `--max-history-highest-marketcap`	Historical highest market cap (USD)
`--min-swaps` / `--max-swaps`	Swap count
`--min-holder-count` / `--max-holder-count`	Holder count
`--min-gas-fee` / `--max-gas-fee`	Gas fee
`--min-renowned-count` / `--max-renowned-count`	KOL / renowned wallet count
`--min-smart-degen-count` / `--max-smart-degen-count`	Smart-money holder count
`--min-bot-degen-count` / `--max-bot-degen-count`	Bot-degen wallet count
`--min-visiting-count` / `--max-visiting-count`	Visitor count
`--min-price-change-percent` / `--max-price-change-percent`	Price change ratio over the interval
`--min-insider-rate` / `--max-insider-rate`	Insider trading ratio (0–1); tokens lacking this field are excluded
`--min-bundler-rate` / `--max-bundler-rate`	Bundle-bot trading ratio (0–1); tokens lacking this field are excluded
`--min-entrapment-ratio` / `--max-entrapment-ratio`	Entrapment trading ratio (0–1); tokens lacking this field are excluded
`--min-top10-holder-rate` / `--max-top10-holder-rate`	Top-10 holder concentration (0–1)
`--min-top70-sniper-hold-rate` / `--max-top70-sniper-hold-rate`	Top-70 sniper holding ratio (0–1)
`--min-dev-team-hold-rate` / `--max-dev-team-hold-rate`	Dev-team holding ratio (0–1); `--min-dev-team-hold-rate` also excludes creator-close tokens
`--min-created` / `--max-created`	Token age window, duration string with a `m` (minutes) / `h` (hours) / `d` (days) suffix, e.g. `30m` / `6h` / `7d`. `--min-created` is a minimum age (excludes younger tokens); `--max-created` a maximum age (excludes older tokens). Note: the raw upstream rank interface accepts minutes only; the openapi-service does not forward this field — it evaluates the age window itself (cutoff = now − duration, computed natively for `m`/`h`/`d`), so `6h` / `7d` work here. Always include a unit suffix — a bare number is not accepted.

Usage Examples

Kline

# Last 1 hour of 1-minute candles
# macOS:
gmgn-cli market kline \
  --chain sol

Use --platform to filter trending results to tokens from specific launchpads only.

`market trending` Response Fields

The response is data.rank — an array of rank items. Each item represents one token.

Basic Info

Field	Description
`address`	Token contract address
`symbol` / `name`	Token ticker and full name
`logo`	Token logo image URL
`chain`	Chain identifier
`total_supply`	Total token supply
`creator`	Creator wallet address
`launchpad_platform`	Launch/pool platform (e.g. `Pump.fun`, `letsbonk`, `pool_meteora`, `fourmeme`)
`exchange`	Current DEX (e.g. `meteora_damm_v2`, `raydium`, `pump_amm`)
`open_timestamp`	Open market listing time (Unix seconds)
`creation_timestamp`	Token creation time (Unix seconds)
`rank`	Position in this trending list (lower = hotter)
`hot_level`	Trending intensity level (higher = hotter)

Price & Market

Field	Description
`price`	Current price in USD
`market_cap`	Market cap in USD (directly available — no calculation needed)
`liquidity`	Current liquidity in USD
`volume`	Trading volume in USD for the queried interval
`history_highest_market_cap`	All-time highest market cap in USD
`initial_liquidity`	Initial liquidity at token launch
`price_change_percent`	Price change % for the queried interval
`price_change_percent1m`	Price change % in last 1 minute
`price_change_percent5m`	Price change % in last 5 minutes
`price_change_percent1h`	Price change % in last 1 hour

Trading Activity

Field	Description
`swaps`	Total swap count in the queried interval
`buys` / `sells`	Buy / sell count in the interval
`holder_count`	Number of unique token holders
`gas_fee`	Average gas fee per transaction

Security & Risk

Field	Chains	Description
`renounced_mint`	SOL	Mint authority renounced (`1` = yes, `0` = no)
`renounced_freeze_account`	SOL	Freeze authority renounced (`1` = yes, `0` = no)
`is_honeypot`	BSC / Base	Honeypot flag (`1` = yes, `0` = no)
`is_open_source`	all	Contract verified (`1` = yes, `0` = no)
`is_renounced`	all	Ownership renounced (`1` = yes, `0` = no)
`buy_tax` / `sell_tax`	all	Tax rate — empty string means `0` (no tax)
`burn_status`	all	Liquidity burn status (e.g. `"none"`, `"burn"`)
`top_10_holder_rate`	all	Top 10 wallets concentration (0–1)
`rug_ratio`	all	Rug pull risk score (0–1)
`is_wash_trading`	all	Wash trading detected (`true` / `false`)
`rat_trader_amount_rate`	all	Ratio of insider/sneak trading volume
`bundler_rate`	all	Ratio of bundle bot trading volume
`entrapment_ratio`	all	Entrapment trading ratio
`sniper_count`	all	Number of sniper wallets at launch
`bot_degen_count` / `bot_degen_rate`	all	Bot degen wallet count / ratio
`dev_team_hold_rate`	all	Dev team holding ratio
`top70_sniper_hold_rate`	all	Top 70 sniper current holding ratio
`lock_percent`	all	Liquidity lock percentage

Dev Status

Field	Description
`creator_token_status`	Dev holding status: `creator_hold` (still holding) / `creator_close` (sold/closed)
`creator_close`	Boolean shorthand for `creator_token_status == creator_close`
`dev_token_burn_ratio`	Ratio of dev's tokens that have been burned

Smart Money

Field	Description
`smart_degen_count`	Number of smart money wallets holding the token
`renowned_count`	Number of renowned / KOL wallets holding the token
`bluechip_owner_percentage`	Ratio of holders that are bluechip wallets (0–1)

Social

Field	Description
`twitter_username`	Twitter / X username (not a full URL — prepend `https://x.com/` to get the link)
`website`	Project website URL
`telegram`	Telegram URL
`cto_flag`	Community takeover flag (`1` = CTO has occurred)

Dexscreener Marketing

Field	Description
`dexscr_ad`	Dexscreener ad placed (`1` = yes)
`dexscr_update_link`	Social links updated on Dexscreener (`1` = yes)
`dexscr_trending_bar`	Paid for Dexscreener trending bar (`1` = yes)
`dexscr_boost_fee`	Dexscreener boost amount paid (0 = none)

Full workflow for discovering market opportunities: docs/workflow-market-opportunities.md

Steps: fetch trending (50 results, safe filters) → AI multi-factor analysis (smart money, volume, momentum, liquidity, maturity) → present top 5 table with rationale → offer deep dive or swap.

When results contain interesting tokens, proceed to full token due diligence: docs/workflow-token-research.md

For new / launchpad tokens (market trenches): apply the structured early project screening workflow that includes security check and smart money entry detection — docs/workflow-early-project-screening.md

For a daily market overview (user asks "what's the market like today", "give me a daily brief", "what is smart money buying today"): combine market trending + market trenches with gmgn-track smartmoney — docs/workflow-daily-brief.md

Token Quality Filter Criteria

When evaluating tokens returned from market trending or market trenches, apply these criteria to quickly separate high-quality opportunities from noise. Do not present raw results without filtering.

Pass / Watch / Skip Criteria

Signal	🟢 Pass	🟡 Watch	🔴 Skip
`smart_degen_count`	≥ 3	1–2	0
`rug_ratio`	< 0.1	0.1–0.3	> 0.3
`creator_token_status`	`creator_close`	—	`creator_hold`
`is_wash_trading`	`false`	—	`true` → skip immediately
`top_10_holder_rate`	< 0.20	0.20–0.50	> 0.50
`liquidity`	> $50k	$10k–$50k	< $10k
`has_social` (or any social field present)	yes	—	no (weak signal only)

Quick disqualification rule: If rug_ratio > 0.3 OR is_wash_trading = true OR is_honeypot = 1 → skip immediately, no further analysis needed.

Strong buy signal combination: smart_degen_count ≥ 3 + rug_ratio < 0.2 + creator_close + is_wash_trading = false + liquidity > $50k → high-quality opportunity, proceed to full token research.

For full due diligence on any token surfaced here: docs/workflow-token-research.md

Token Lifecycle Stage

Use field combinations to determine what stage a token is in. This affects how signals should be interpreted.

Stage 1 — Early (New Born)

Indicators:

creation_timestamp < 1 hour ago
hot_level low or just starting to rise
smart_degen_count = 0, renowned_count = 0

Interpretation: Too early for smart money signals. No on-chain track record. High risk, high potential reward. Wait for Stage 2 confirmation before acting. Only the most risk-tolerant traders enter here.

Stage 2 — Breakout

Indicators:

smart_degen_count ≥ 3 AND rising
Volume surging (compare swaps_1h vs swaps_24h / 24 — significantly higher)
price_change_percent1h > 20%
creator_token_status = creator_hold is OK at this stage (dev hasn't distributed yet)

Interpretation: Strongest entry signal. Smart money is accumulating. Verify security before acting. This window is often short — act on confirmation, not anticipation.

Stage 3 — Distribution

Indicators:

creator_token_status = creator_close (dev has sold their allocation)
renowned_count buying (late social signal — KOLs often enter after smart money)
smart_degen_count plateauing or declining
Volume still high but momentum slowing

Interpretation: Late stage entry. Smart money may be exiting into retail/KOL demand. Higher risk for new entries. If already holding from Stage 2, evaluate exit levels.

Stage 4 — Decline

Indicators:

Volume declining across all windows
holder_count declining
rat_trader_amount_rate high (insider/sneak trading dominating)
smart_degen_count = 0 or clearly declining

Interpretation: Avoid new entries entirely. If still holding, consider exiting. The opportunity has likely passed.

`market trenches` Parameters

Intent → --type mapping (always specify --type explicitly):

User intent	`--type` value
"new tokens", "just launched", "newly created", "latest tokens"	`new_creation`
"about to graduate", "near completion", "bonding curve almost full"	`near_completion`
"graduated tokens", "already on DEX", "open market tokens"	`completed`
No specific stage mentioned	omit `--type` (returns all three)

Parameter	Required	Description
`--chain`	Yes	`sol` / `bsc` / `base` / `eth` / `robinhood` / `arc` / `stable`
`--type`	No	Categories to query, repeatable: `new_creation` / `near_completion` / `completed` (default: all three)
`--launchpad-platform`	No	Launchpad platform filter, repeatable (default: all platforms for the chain)
`--limit`	No	Max results per category, max 80 (default: 80)
`--filter-preset`	No	Named server-side filter preset: `safe` / `smart-money` / `strict`
`--sort-by`	No	Client-side sort per category: `smart_degen_count` / `renowned_count` / `volume_24h` / `volume_1h` / `swaps_24h` / `swaps_1h` / `rug_ratio` / `holder_count` / `usd_market_cap` / `created_timestamp`
`--direction`	No	Sort direction: `asc` / `desc` (default: `desc`; `asc` for `rug_ratio`)
`--min-` / `--max-`	No	Server-side filter range flags — see Filter Fields Reference below

--launchpad-platform values by chain (omit --launchpad-platform to use all of the chain's platforms):

Chain	Platforms
`sol`	`Pump.fun` / `pump_mayhem` / `pump_mayhem_agent` / `pump_agent` / `letsbonk` / `bonkers` / `bags` / `memoo` / `liquid` / `bankr` / `zora` / `surge` / `anoncoin` / `moonshot_app` / `wendotdev` / `heaven` / `sugar` / `token_mill` / `believe` / `trendsfun` / `trends_fun` / `jup_studio` / `Moonshot` / `boop` / `ray_launchpad` / `meteora_virtual_curve` / `xstocks`
`bsc`	`fourmeme` / `fourmeme_agent` / `bn_fourmeme` / `four_xmode_agent` / `cubepeg` / `likwid` / `goplus_creator` / `goplus_skills` / `openfour` / `flap` / `flap_stocks` / `flap_aioracle` / `clanker` / `lunafun`
`base`	`clanker` / `bankr` / `flaunch` / `zora` / `zora_creator` / `baseapp` / `basememe` / `virtuals_v2` / `klik`
`eth`	`trench` / `clanker` / `klik` / `livo` / `stroid` / `pool_uniswap_v2` / `pool_uniswap_v3` / `printr`
`arc`	`dyorfun_v3` / `dyorswap` / `trench` / `onmifun` / `sharcfun` / `klik`
`stable`	`dyorfun_v3` / `dyorswap` / `trench`

Filter Presets

Presets are applied server-side: the API filters tokens before returning results.

Preset	Server-side filters applied
`safe`	`max_rug_ratio=0.3` + `max_bundler_rate=0.3` + `max_insider_ratio=0.3`
`smart-money`	`min_smart_degen_count=1`
`strict`	`max_rug_ratio=0.3` + `max_bundler_rate=0.3` + `max_insider_ratio=0.3` + `min_smart_degen_count=1` + `min_volume_24h=1000`

Preset + explicit flag interaction: Explicit filter flags always override preset values. For example, --filter-preset safe --max-rug-ratio 0.1 applies the safe preset but overrides rug_ratio threshold to 0.1.

All filter flags are sent as part of the API request body (server-side) — the server filters tokens before returning results. Use --limit 80 (the default maximum) to maximise the pool.

Response fields: data.new_creation, data.pump, data.completed — each is an array of RankItem (same fields as market trending rank items). Important: data.pump in the response corresponds to --type near_completion in the request. The API always returns this category under the key pump, not near_completion.

Server-Side Filter Fields

All filter flags are sent as part of the API request body — the server filters tokens before returning results. Flags follow the naming convention --min-{field} / --max-{field}.

Flag pair	Type	Description
`--min-volume-24h` / `--max-volume-24h`	float	24h trading volume (USD)
`--min-net-buy-24h` / `--max-net-buy-24h`	float	24h net buy volume (USD)
`--min-swaps-24h` / `--max-swaps-24h`	int	24h total swap count
`--min-buys-24h` / `--max-buys-24h`	int	24h buy count
`--min-sells-24h` / `--max-sells-24h`	int	24h sell count
`--min-visiting-count` / `--max-visiting-count`	int	Visitor count
`--min-progress` / `--max-progress`	float	Bonding curve progress (0–1)
`--min-marketcap` / `--max-marketcap`	float	Market cap (USD)
`--min-liquidity` / `--max-liquidity`	float	Liquidity (USD)
`--min-created` / `--max-created`	duration	Token age — unit suffix recommended: seconds (`30s`, `10s`) or minutes (`0.5m`, `1m`, `5m`, `30m`). Bare numbers (e.g. `5`) are treated as minutes with a warning.
`--min-holder-count` / `--max-holder-count`	int	Holder count
`--min-top-holder-rate` / `--max-top-holder-rate`	float	Top-10 holder concentration (0–1)
`--min-rug-ratio` / `--max-rug-ratio`	float	Rug pull risk score (0–1)
`--min-bundler-rate` / `--max-bundler-rate`	float	Bundle-bot trading ratio (0–1)
`--min-insider-ratio` / `--max-insider-ratio`	float	Insider trading ratio (0–1)
`--min-entrapment-ratio` / `--max-entrapment-ratio`	float	Entrapment/Phishing trading ratio (0–1)
`--min-private-vault-hold-rate` / `--max-private-vault-hold-rate`	float	Private vault holding ratio (0–1)
`--min-top70-sniper-hold-rate` / `--max-top70-sniper-hold-rate`	float	Top-70 sniper holding ratio (0–1)
`--min-bot-count` / `--max-bot-count`	int	Bot wallet count
`--min-bot-degen-rate` / `--max-bot-degen-rate`	float	Bot-degen wallet ratio (0–1)
`--min-fresh-wallet-rate` / `--max-fresh-wallet-rate`	float	Fresh wallet ratio (0–1)
`--min-total-fee` / `--max-total-fee`	float	Total fee
`--min-smart-degen-count` / `--max-smart-degen-count`	int	Smart-money holder count
`--min-renowned-count` / `--max-renowned-count`	int	KOL / renowned wallet count
`--min-creator-balance-rate` / `--max-creator-balance-rate`	float	Creator holding ratio (0–1)
`--min-creator-created-count` / `--max-creator-created-count`	int	Creator's total token creation count
`--min-creator-created-open-count` / `--max-creator-created-open-count`	int	Creator's graduated token count
`--min-creator-created-open-ratio` / `--max-creator-created-open-ratio`	float	Creator's graduation ratio (0–1)
`--min-x-follower` / `--max-x-follower`	int	Twitter / X follower count
`--min-twitter-rename-count` / `--max-twitter-rename-count`	int	Twitter rename count
`--min-tg-call-count` / `--max-tg-call-count`	int	Telegram call count

Trenches Filter Examples

`market trenches` Response Fields

Basic Info

Field	Description
`address`	Token contract address
`symbol` / `name`	Token symbol and name
`launchpad_platform`	Launch platform (e.g. `Pump.fun`, `letsbonk`)
`exchange`	Current exchange (e.g. `pump_amm`, `raydium`)
`usd_market_cap`	Market cap in USD
`liquidity`	Liquidity in USD
`total_supply`	Total token supply
`created_timestamp`	Creation time (Unix seconds)
`open_timestamp`	Open market listing time (Unix seconds, `completed` only)
`complete_timestamp`	Bonding curve completion time (Unix seconds)
`complete_cost_time`	Time from creation to completion in seconds

Trading Data

Field	Description
`swaps_1m` / `swaps_1h` / `swaps_24h`	Swap count per time window
`volume_1h` / `volume_24h`	Trading volume in USD
`buys_24h` / `sells_24h`	Buy / sell count in 24h
`net_buy_24h`	Net buy volume in 24h
`holder_count`	Number of token holders

Security & Risk

Field	Chains	Description
`renounced_mint`	SOL	Whether mint authority is renounced (SOL-specific concept; always `false` on EVM chains)
`renounced_freeze_account`	SOL	Whether freeze authority is renounced (SOL-specific concept; always `false` on EVM chains)
`burn_status`	all	Liquidity burn status
`rug_ratio`	all	Rug pull risk ratio
`top_10_holder_rate`	all	Top 10 holders concentration ratio
`rat_trader_amount_rate`	all	Insider / sneak trading volume ratio
`bundler_trader_amount_rate`	all	Bundle trading volume ratio
`is_wash_trading`	all	Whether wash trading is detected
`sniper_count`	all	Number of sniper wallets
`suspected_insider_hold_rate`	all	Suspected insider holding ratio
`open_source`	all	Whether contract source code is verified (`"yes"` / `"no"` / `"unknown"`)
`owner_renounced`	all	Whether contract ownership is renounced (`"yes"` / `"no"` / `"unknown"`)
`is_honeypot`	BSC / Base	Whether token is a honeypot (`"yes"` / `"no"`); returns empty string on SOL (not applicable)
`buy_tax`	all	Buy tax ratio (e.g. `0.03` = 3%)
`dev_team_hold_rate`	all	Dev team holding ratio

Dev Holdings

Field	Description
`creator_token_status`	Dev holding status (e.g. `creator_hold`, `creator_close`)
`creator_balance_rate`	Dev holding ratio as a proportion of total supply

Smart Money

Field	Description
`smart_degen_count`	Number of smart money holders
`renowned_count`	Number of renowned wallet holders (KOL)

Social Media

Field	Description
`twitter`	Twitter / X link
`telegram`	Telegram link
`website`	Website link
`instagram`	Instagram link
`tiktok`	TikTok link
`has_at_least_one_social`	Whether any social media link exists
`x_user_follower`	Twitter follower count
`cto_flag`	Whether community takeover (CTO) has occurred

Dexscreener Marketing

Field	Description
`dexscr_ad`	Whether a Dexscreener ad has been placed
`dexscr_update_link`	Whether social links have been updated on Dexscreener
`dexscr_trending_bar`	Whether paid for Dexscreener trending bar placement
`dexscr_boost_fee`	Amount paid for Dexscreener boost (0 = none)

After fetching trenches results, apply the Token Quality Filter Criteria section before presenting tokens to the user. Do not dump raw results — filter first, then surface the strongest candidates.

Trenches Filter Examples

Solana Trenches Examples

BSC Trenches Examples

Base Trenches Examples

ETH Trenches Examples

Arc Trenches Examples

Stable Trenches Examples

Output Format

`market kline` — Price Summary

After fetching candles, present a brief price analysis. Do not dump raw candle arrays.

`market trending` — Top Tokens Table

Present the top results (default: top 10, or as requested) as a table:

Where Signal = quality flag derived from the token's data:

🟢 Pass: smart_degen_count ≥ 3 AND rug_ratio < 0.2 AND is_wash_trading = false
🔴 Skip: rug_ratio > 0.3 OR is_wash_trading = true OR is_honeypot = 1
🟡 Watch: everything else

Then give a one-line highlight for any standout tokens (e.g. "TOKEN1 has 12 smart money holders and +85% in 1h — 🟢 strong signal").

`market trenches` — Grouped by Category

Present each category separately with a header:

`market signal` Parameters

Chains: sol / bsc / robinhood / arc / stable only. Maximum 50 results per group — use multiple groups via --groups to cover different signal types in a single request.

Single-group (individual flags):

Do not pass signal types 14, 15, or 16 in signal_type / --signal-type / --groups JSON — OpenAPI returns 400 if any group includes them. Omitting --signal-type (empty filter) still queries all types upstream; responses may still include 14–16 in that case.

Option	Required	Description
`--chain`	Yes	`sol` / `bsc`
`--signal-type`	No	Signal type(s), repeatable (1–21, default: all). See Signal Types below.
`--mc-min`	No	Min market cap at trigger time (USD)
`--mc-max`	No	Max market cap at trigger time (USD)
`--trigger-mc-min`	No	Min market cap at signal trigger moment (USD)
`--trigger-mc-max`	No	Max market cap at signal trigger moment (USD)
`--total-fee-min`	No	Min total fees paid (USD)
`--total-fee-max`	No	Max total fees paid (USD)
`--min-create-or-open-ts`	No	Min token creation or open timestamp (Unix seconds string)
`--max-create-or-open-ts`	No	Max token creation or open timestamp (Unix seconds string)

Multi-group override:

Pass --groups '<json_array>' to query multiple filter groups in a single request. The upstream executes all groups in parallel and merges results sorted by trigger_at descending. When --groups is present, all individual flags above are ignored.

Signal Types

Value	Name	Description
1	SignalType1	General signal (K-line price spike)
2	SignalTypeDexAd	Dex ad placement
3	SignalTypeDexUpdateLink	Dex social link updated
4	SignalTypeDexTrendingBar	Dex trending bar
5	SignalTypeDexBoost	Dex Boost
6	SignalTypePriceUp	Price spike
7	SignalTypePriceATH	All-time high price
8	SignalTypeMcpKeyLevel	Market cap key level
9	SignalTypeLive	Live stream
10	SignalTypeBundlerSell	Bundler sell
11	SignalTypeCto	Community takeover (CTO)
12	SignalTypeSmartDegenBuy	Smart money buy
13	SignalTypePlatformCall	Platform call
14	SignalTypeLargeAmountBuy	Large amount buy
15	SignalTypeMultiBuy	Multiple buys
16	SignalTypeMultiLargeBuy	Multiple large buys
17	SignalTypeBagsClaims	Bags Claim
18	SignalTypePumpClaims	Pump Claim
19	SignalTypePlatformCallV2	Platform call (V2)
20	SignalTypeKOLBuy	KOL buy
21	SignalTypeBankerClaims	Banker Claim (Base chain Banker platform claim fee)

`market signal` Response Fields

Each item in the response array is one signal event:

Field	Type	Description
`id`	string	Signal event ID
`token_address`	string	Token contract address
`signal_type`	number	Signal type (1–21, see Signal Types above)
`trigger_at`	number	Unix timestamp (seconds) when the signal was triggered
`trigger_mc`	number	Market cap at signal trigger time (USD)
`first_trigger_mc`	number	Market cap at the very first trigger for this token (USD)
`market_cap`	number	Current market cap (USD)
`ath`	number	All-time high market cap (USD)
`signal_times`	number	Total number of times this signal has triggered for this token
`signal_times_by_type`	object	Signal trigger count broken down by type
`cur_data`	object	Real-time token stats at query time (see below)
`data`	object	Full upstream snapshot at trigger time (chain-specific, raw passthrough)

cur_data fields:

Field	Type	Description
`top_10_holder_rate`	number	Top 10 holder concentration ratio (0–1)
`holder_count`	number	Current holder count
`liquidity`	number	Current liquidity (USD)

Usage Examples

`market hot-searches` Parameters

Returns the hot-search ranking — the tokens people are searching for most right now, ranked by visiting_count (search heat). Cross-chain top-500 ranking; one request can cover several chains at once. Use this for "most searched tokens", "hot search list", "热搜榜", "what is everyone looking at" — this is distinct from market trending (ranked by swap activity), which answers "what is being traded most."

Option	Description
`--chain <chain...>`	Repeatable. `sol` / `bsc` / `base` / `eth` / `robinhood` / `arc` / `stable`. Omit to query the default 9-chain set (sol / bsc / base / eth / arbitrum / hyperevm / robinhood / arc / stable, each at `24h` with chain-appropriate safety filters).
`--interval <interval>`	`1m` / `5m` / `1h` / `6h` / `24h` (default `24h`). Applies to every `--chain` provided.
`--limit <n>`	Max results per chain (default `500`).
`--filter <tag...>`	Repeatable boolean filter tags (the downstream `filter.filters` array). ⚠️ SOL defaults: `renounced frozen`; EVM defaults: `not_honeypot verified renounced`. Omitting `--filter` is NOT "no filter" — the server applies chain defaults. See the Filter Tags table below for the exact vocabulary.
`--min-* / --max-* <n>`	Numeric range bounds, same metric names as `market trending` (e.g. `--min-liquidity`, `--max-marketcap`, `--min-smart-degen-count`). Translated server-side per `--interval`. `--min-created` / `--max-created` are token-age durations. See the Range Filters table below.
`--params <json>`	Full override: a JSON array of param objects. When provided, `--chain` / `--interval` / `--limit` / `--filter` and all range flags are ignored. Filter fields are flattened onto each param (no nested `filter` object): `{ "label": "...", "chain": "...", "interval": "...", "filters": [...], "limit": 500, "min_liquidity": 1000 }` — a param accepts `filters`, `limit`, `min_created`/`max_created`, and rank-style `min_<metric>`/`max_<metric>` keys.

`market hot-searches` Filter Tags (`--filter` / `filter.filters`)

The downstream (gmgn rank filter-service) evaluates each tag as an AND condition — a token must pass every tag to stay in the list. Unknown tags are silently accepted but do nothing (pass-through), so an unrecognised tag will NOT filter anything — spelling matters. This tag set is the filter-service vocabulary and differs slightly from market trending's tag names (see the alias note below).

These are the only recognised tags (anything else is a no-op):

Tag	Chains	Passes when
`renounced`	sol / EVM	sol: mint authority renounced (`renounced_mint == 1`); EVM: owner renounced (`is_renounced == 1`; lenient — nil passes)
`frozen`	sol only	freeze authority renounced (`renounced_freeze_account == 1`); non-sol always fails
`is_burnt`	all	LP pool burned (`burn_status == "burn"`)
`token_burnt`	all	creator burned tokens (`dev_token_burn_ratio > 0`)
`not_wash_trading`	all	not flagged as wash trading
`not_honeypot`	EVM	not a honeypot (`is_honeypot == 0`; lenient — nil passes)
`verified`	EVM	contract open-source (`is_open_source == 1`; lenient — nil passes)
`locked`	EVM	liquidity locked ≥ 50% (`lock_percent >= 0.5`)
`has_social`	all	has Twitter, Telegram, or Website
`distribed`	all	top-10 holder rate in (0, 0.3] (well distributed)
`not_risk`	all	composite low-risk filter (sol: liquidity≥4000 + mint renounced + top10<0.3 + freeze renounced + LP burned; EVM: not honeypot + liquidity≥4000 + open-source + renounced + lock≥0.5)
`img_not_duplicate`	all	avatar image not duplicated (`image_dup == "0"`)
`social_not_duplicate`	all	social links not shared (`twitter_dup == 0 && telegram_dup == 0 && website_dup == 0`)
`creator_hold`	all	dev still holding (not `creator_close`)
`creator_close`	all	dev sold/closed (`creator_token_status == "creator_close"`)
`dexscr_update_link`	all	social links updated on DexScreener (`> 0`)
`launching`	all	still on the launchpad bonding curve (`launchpad_status == "0"`); pair with `migrated` to allow both
`migrated`	all	graduated / migrated to DEX (`launchpad_status == "1"`); pair with `launching` to allow both
`hide_b20`	base only	token standard is not `b20` (no-op on non-base)
`hide_non_b20`	base only	token standard is `b20` (no-op on non-base)

⚠️ Different names than market trending. This path uses launching / migrated (NOT is_internal_market / is_out_market) and img_not_duplicate / social_not_duplicate (NOT not_image_dup / not_social_dup). Tags that market trending supports but this endpoint does not recognise (they become silent no-ops here): dexscr_ad, dexscr_trending_bar, dexscr_boost, cto_flag, is_internal_market, is_out_market, not_image_dup, not_social_dup.

`market hot-searches` Range Filters (`--min-` / `--max-`)

Numeric bounds use the same rank-style metric names as market trending. They are sent flattened on each param and translated server-side to the downstream field for the param's --interval. Closed intervals; metrics the downstream cannot read are dropped (not silent no-ops on the wire — they are removed before the request).

Flag pair	Type	Metric
`--min-volume` / `--max-volume`	float	Trading volume (USD) — bound to the `--interval` window
`--min-swaps` / `--max-swaps`	int	Swap count — bound to the `--interval` window
`--min-price-change-percent` / `--max-price-change-percent`	float	Price change ratio — only `1m` / `5m` / `1h`; dropped for `6h` / `24h`
`--min-liquidity` / `--max-liquidity`	float	Liquidity (USD)
`--min-marketcap` / `--max-marketcap`	float	Market cap (USD)
`--min-history-highest-marketcap` / `--max-history-highest-marketcap`	float	All-time-high market cap (USD)
`--min-holder-count` / `--max-holder-count`	int	Holder count
`--min-gas-fee` / `--max-gas-fee`	float	Gas fee
`--min-renowned-count` / `--max-renowned-count`	int	KOL / renowned holder count
`--min-smart-degen-count` / `--max-smart-degen-count`	int	Smart-money holder count
`--min-bot-degen-count` / `--max-bot-degen-count`	int	Bot-degen wallet count
`--min-visiting-count` / `--max-visiting-count`	int	Visitor count
`--min-insider-rate` / `--max-insider-rate`	float	Insider trading ratio (0–1); tokens lacking this field are excluded
`--min-bundler-rate` / `--max-bundler-rate`	float	Bundle-bot trading ratio (0–1); tokens lacking this field are excluded
`--min-entrapment-ratio` / `--max-entrapment-ratio`	float	Entrapment trading ratio (0–1); tokens lacking this field are excluded
`--min-top10-holder-rate` / `--max-top10-holder-rate`	float	Top-10 holder concentration (0–1)
`--min-top70-sniper-hold-rate` / `--max-top70-sniper-hold-rate`	float	Top-70 sniper holding ratio (0–1)
`--min-dev-team-hold-rate` / `--max-dev-team-hold-rate`	float	Dev-team holding ratio (0–1)
`--min-created` / `--max-created`	duration	Token age window (`30m` / `6h` / `7d`). `min_created` = minimum age; `max_created` = maximum age

Notes on behaviour:

--chain all is not valid. To aggregate across chains, pass --chain multiple times (or omit --chain for the default 9-chain set).
When you pass --chain but omit --filter, the server applies the chain-appropriate default filters — so each chain is filtered even without an explicit --filter.
Different chains return different counts: a chain's token count depends on how many of its tokens made the global top-500 (sol is usually the largest).

`market hot-searches` Response Fields

The response data is an array. Each element is one (interval, chain) result block:

Field	Type	Description
`interval`	string	The interval for this block
`chain`	string	The chain for this block
`version`	string	Subscription version — persist it for WebSocket reconnect
`tokens`	array	Ranked tokens (search heat desc), max 500. Each token carries a 1-based `rank`

Token fields are the same long-form fields as market trending — the server maps the upstream shortcodes for you, so you read visiting_count / market_cap / symbol directly (NOT v_c / mc / s). Key fields:

Field	Description
`address`	Token contract address
`chain`	Chain
`name` / `symbol`	Token name / ticker
`price`	Current price (USD)
`visiting_count`	Primary ranking key — search / visit heat
`market_cap`	Market cap (USD)
`volume`	Volume in this interval (USD)
`liquidity`	Liquidity (USD)
`swaps` / `buys` / `sells`	Swap / buy / sell counts
`holder_count`	Holder count
`rank`	1-based position within the block

See the market trending Response Fields section above for the full field set — hot-searches tokens use the identical RankItem shape.

`market hot-searches` Usage Examples

`market hot-searches` — Output Format

Present per chain, ranked by visiting_count (search heat):

`market search` Parameters

Look up a specific token or wallet the user names — by token name, symbol, contract address, wallet address, or ENS. A single request returns both matching tokens (coins) and wallets (wallets). Use this when the user provides something concrete to find; use market trending / market hot-searches when they want to browse rankings instead.

Parameter	Required	Description
`--query` / `-q`	Yes	Search keyword — token name, symbol, contract address, wallet address, or ENS. After stripping invisible/control characters it must be 1–100 Unicode characters.
`--chain`	No	Scope results to one chain. Omit to search all chains. Accepts `all` and any enabled chain (see Supported Chains — includes the 9 core chains plus dynamically-enabled ones like `tron` / `monad` / `megaeth` / `xlayer` / `hyperevm`).
`--launchpad-platform`	No	Exact launchpad platform filter, repeatable, max 50 values (e.g. `pump` / `moonshot` / `raydium` / `pinksale`). Filters `coins` only — does not affect `wallets`.
`--is-og`	No	`true` = only OG tokens; `false` = only non-OG. Omit for no OG filter. Coins only.
`--is-launched`	No	`true` = only already-launched (open-market) tokens; `false` or omit applies no launch filter. Coins only.
`--order-by`	No	Only `weight` is accepted — sorts `coins` by weighted relevance score descending and drops honeypot tokens. Coins only.

Behavior notes:

--launchpad-platform, --is-og, --is-launched, and --order-by only shape the coins list. The wallets list is never affected by these flags.
wallets are capped at 50 results.
The response schema is a raw additive passthrough from the downstream search_v3 API, and all string fields are metadata-sanitized before return. New fields may appear without notice — do not assume a closed field set; look up unfamiliar fields rather than guessing.

`market search` Response Fields

data contains two arrays: coins (matching tokens) and wallets (matching wallets).

coins[] — matching tokens

Field	Description
`chain`	Chain identifier
`address`	Token contract address
`name` / `symbol`	Token name / ticker
`price`	Current price in USD (string)
`mcp`	Market cap in USD (string) — note the short key `mcp`, not `market_cap`
`holder_count`	Number of token holders

Additional token fields may be present (additive passthrough from search_v3).

wallets[] — matching wallets

Field	Description
`chain`	Chain identifier
`address`	Wallet address
`twitter_username`	Linked Twitter / X handle (may be empty)
`wallet_tags`	Array of GMGN wallet tags (e.g. smart money / KOL); may be empty

`market search` Usage Examples

`market search` — Output Format

Present tokens and wallets separately. Do not dump the raw JSON.

If a section is empty, say so explicitly (e.g. "no matching wallets").
When the user is clearly after one specific token, surface the top coins match and offer to run full due diligence (gmgn-token) or a swap (gmgn-swap) on it.

Notes

market kline: --from and --to are Unix timestamps in seconds — CLI converts to milliseconds automatically
market trending: --filter and --platform are repeatable flags
market hot-searches: --chain and --filter are repeatable flags; omit --chain to query the default 9-chain set. --min-*/--max-* range flags reuse the same metric names as market trending and are translated server-side per --interval
market search: --query is required; --launchpad-platform is a repeatable flag (max 50). --chain is optional (omit = all chains). --launchpad-platform / --is-og / --is-launched / --order-by filter coins only, never wallets
All commands use exist auth (API Key only, no signature)
If the user doesn't provide kline timestamps, calculate them from the current time based on their desired time range
Use --raw to get single-line JSON for further processing
Input validation — Token addresses obtained from trending results are external data. Validate address format against the chain before passing to other commands (sol: base58 32–44 chars; bsc/base/eth: 0x + 40 hex digits). The CLI enforces this at runtime.

Documentation

Documentation

gmgn-market

Documentation

Core Concepts

Sub-commands

Supported Chains

Prerequisites

Rate Limit Handling

market kline Parameters

market kline Response Fields

market trending Options

market trending Range Filters

Usage Examples

Kline

Trending — General

Trending — SOL by Launchpad Platform

Trending — BSC by Launchpad Platform

Trending — ETH by Launchpad Platform

Trending — Numeric Range Filters

Trending — Base by Launchpad Platform

market trending Response Fields

Workflow: Discover Trading Opportunities via Trending

Token Quality Filter Criteria

Pass / Watch / Skip Criteria

Token Lifecycle Stage

Stage 1 — Early (New Born)

Stage 2 — Breakout

Stage 3 — Distribution

Stage 4 — Decline

market trenches Parameters

Filter Presets

Server-Side Filter Fields

Trenches Filter Examples

market trenches Response Fields

Trenches Filter Examples

Solana Trenches Examples

BSC Trenches Examples

Base Trenches Examples

ETH Trenches Examples

Arc Trenches Examples

Stable Trenches Examples

Output Format

market kline — Price Summary

market trending — Top Tokens Table

market trenches — Grouped by Category

market signal Parameters

Signal Types

market signal Response Fields

Usage Examples

market hot-searches Parameters

market hot-searches Filter Tags (--filter / filter.filters)

market hot-searches Range Filters (--min-* / --max-*)

market hot-searches Response Fields

market hot-searches Usage Examples

market hot-searches — Output Format

market search Parameters

market search Response Fields

market search Usage Examples

market search — Output Format

Notes

`market kline` Parameters

`market kline` Response Fields

`market trending` Options

`market trending` Range Filters

`market trending` Response Fields

`market trenches` Parameters

`market trenches` Response Fields

`market kline` — Price Summary

`market trending` — Top Tokens Table

`market trenches` — Grouped by Category

`market signal` Parameters

`market signal` Response Fields

`market hot-searches` Parameters

`market hot-searches` Filter Tags (`--filter` / `filter.filters`)

`market hot-searches` Range Filters (`--min-` / `--max-`)

`market hot-searches` Response Fields

`market hot-searches` Usage Examples

`market hot-searches` — Output Format

`market search` Parameters

`market search` Response Fields

`market search` Usage Examples

`market search` — Output Format