What problem does it solve? Shadow, deprecated, and versioned APIs often retain weaker authorization or schema validation than current endpoints, but testing them safely requires strict scope control and evidence-based confirmation rather than blind scanning. ## Core Features & Use Cases - Version and Spec Differencing: Builds baselines of public, legacy, mobile, and documented API routes, then compares authorization, schema, and business semantics across versions. - Evidence-Gated Validation: Enforces a baseline → single-variable probe → post-baseline → server/browser oracle → evidence workflow, treating WAF blocks, captchas, and timeouts as inconclusive rather than findings. - Scope and Stop Controls: Halts on cross-host spread, bulk enumeration, third-party data, or irreversible side effects, and routes confirmed object-level issues to IDOR or API misconfiguration workflows. - Use Case: During an authorized assessment, you discover a deprecated v1 endpoint in old mobile traffic. Use this Skill to verify, on your own account and objects, whether the legacy route lacks the server-side authorization checks present in the current API. ## Quick Start Use $hunt-shadow-api to plan an evidence-gated, authorized validation path for the legacy API endpoints found in scope.
