Token depth / price impact (per pool)

Per-pool price-impact / slippage — "how much SOL to move price N%" and the impact + tokens received for each buy size. For every pool: spot_price_sol, quotes[] per requested SOL size (tokens_out, avg_price_sol, price_impact_pct), and to_move_price (SOL to move price 1%/5%/10%). Exact for constant-product AMMs (PumpSwap, Raydium v4/CPMM, Meteora DAMM — served from streamed reserves, source: "stream"); pump.fun / bonk bonding curves priced from one live read of the curve's virtual reserves (source: "live_rpc"). Impact is per-pool, not router-optimal; concentrated-liquidity pools (Raydium CLMM, Orca, Meteora DLMM) and unclassified pools return under unsupported_pools[] with a reason instead of a wrong number. Concentrated depth models (rollout behind server flags, off by default): when enabled, Meteora DLMM pools are quoted with the program's own integer bin math from one same-slot snapshot of the pair and a bounded bin-array window (model: "concentrated", model_detail: "meteora_dlmm_bins", fee_basis: "dynamic_fee_at_quote_time", bins_window), at most 3 DLMM pools per request; Raydium CLMM pools likewise with the program's own integer tick math (Q64.64 sqrt price, tick arrays, AmmConfig trade fee) from one same-slot snapshot of the pool, its config and the tick arrays in the buy direction (model_detail: "raydium_clmm_ticks", fee_basis: "amm_config_at_quote_time", ticks_window), at most 3 CLMM pools per request; Meteora DAMM v2 pools get a number only when their Pool account is proven and full-range (model_detail: "meteora_damm_v2_full_range", pool_account, fee = the venue default, not the pool's own fee schedule), otherwise they return under unsupported_pools[] with a damm_v2_* reason, never a generic constant-product number; a size that would cross past the loaded ticks has status: "exceeds_loaded_ticks"; every quote then carries a status, and a size the loaded window cannot fill has status: "exceeds_loaded_bins" with null numbers (never a constant-product fallback). The response then also carries pool_selection (largest known pool vs the pool depth is reported for; routing: "single_pool_only", multi-pool routing is not computed). PRO+.