Get a Robinhood Chain token verdict, holders, tax, sell check

Use when you hold or are about to trade one pons v2 token on Robinhood Chain and need a verdict by a fixed public rule, its holders, creator tax, deployer record, ring screen and an exact sell check; to find launches use GET /v1/rhc/launches/recent. Not for Solana mints. The verdict (avoid / caution / no_flags_observed, the fixed public rule LABELS rhc_verdict at /v1/labels, with basis, reason and up to three reasons carrying their evidence and measured base rate): avoid while a charged buy pays >= 618 bps of snipe tax or when the 3 s holder structure matched the ring rule; caution on a creator tax >= 500 bps, a top holder >= 50%, a deployer with >= 3 earlier launches and no graduation, a curve at <= 50% of its peak price 30 min after launch without graduating, a missing or pending 3 s snapshot, or a completed or graduated curve. deployer_record: the deployer's earlier launches on our tape, how many graduated or matched the ring rule at 3 s, the median peak and terminal multiples. sell_check: buy and sell tax in bps, the exact quote for selling 1% of supply and a 0.01 ETH round trip in bps from the recorded reserves (graduated tokens: the pool's taxes, no quote). Full structure card for ONE pons v2 curve on Robinhood Chain, addressed by curve or token address (0x…): launch facts (block, deployer, pair token, graduation threshold), raised / progress / price multiple vs launch (exact curve reserves, ETH-paired curves), the launch's trade fee and creator tax in bps (fees block; the creator tax is charged on every buy and sell and is invisible to three-word event parsers), snipe-tax activity, holder ledger concentration (top-1 / top-5 / HHI / deployer share), same-block direct-buy cluster share and wallets, max direct buys in one 100 ms block, terminal-vs-direct route mix with terminal holdings share, flow (buys / sells / unique buyers / new buyers in the last 2 and 6 s / last trade age / volumes), lifecycle (completed / graduated blocks and delays, refunds), the trade_cost block (for a 0.01 and a 0.05 ETH clip at the curve's reserves now, exact with fee and creator tax on both legs and own impact: fill price vs marginal, the immediate round trip, and the price rise from now needed to break even), and the ring block: the same-block direct-buy cluster screen (unique_buyers >= 8 and same-block direct-buy cluster share >= 0.5) our own capture measured at 14.5% of launches, 47% dumped, median 0.37x terminal; matching timing is not proof of coordination, and on pons v2 such a cluster is often the team's own opening bundle, exempt from the snipe tax at launch. coverage=full for curves launched inside our event window (last ~2 h, trades observed from block 0); thin = launch facts + lifecycle only, with a reason. Always 200 for a valid address.