hunt-api-reverse

Reconstructs API schemas, state machines, and auth boundaries from live request and response evidence.

10|3|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-api-reverse-baiqigo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-api-reverse
Source: https://github.com/baiqigo/baiqi-redteam-lab/tree/main/.agents/skills/hunt-api-reverse
Command: npx skills add https://github.com/baiqigo/baiqi-redteam-lab --skill hunt-api-reverse-baiqigo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When testing a live API without documentation, testers often jump straight to payloads without understanding the endpoint's structure. This Skill provides a disciplined methodology to reverse-engineer an API's schema, state machine, authentication boundaries, and hidden routes from observed request/response behavior before attempting exploitation. ## Core Features & Use Cases - Parameter Semantics Matrix: Builds a baseline-vs-probe comparison matrix where each probe changes only one variable (parameter, encoding, or state) to infer types, required fields, defaults, and constraints. - Adaptive Decision Tree: Guides the tester to deepen schema inference, pivot on rate limits, backtrack on catch-all routes, or wait for new signals based on response classification. - Structured Handoff: Routes discovered artifacts (object IDs, writable fields, tokens, callbacks, templates) to specialized follow-up skills such as IDOR, SQLi, JWT, SSRF, or SSTI analysis. - Use Case: During an authorized assessment, you capture a /api/v2/user endpoint returning different schemas for detail=true vs full=true. The Skill walks you through isolating the route selector, mapping the state machine, and handing the discovered object ID to IDOR testing. ## Quick Start Ask the agent to reverse-engineer the schema and state machine of a captured API endpoint using its saved request and response samples.

Frequently Asked Questions about hunt-api-reverse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reverse-engineer an undocumented API endpoint?

Start with a known-valid baseline request, then change one parameter, encoding, or state variable per probe and compare status, headers, body schema, and timing. This builds a parameter semantics matrix that reveals types, required fields, and handler-switching route selectors.

How to find hidden or shadow API routes during testing?

Compare behavior across route selectors like route, full, detail, and fields, plus alternate same-origin ports and v1/v2 or web/mobile paths. Repeatable schema differences indicate separate handlers worth dedicated verification.

What should I do when API probing hits rate limits or 429 responses?

Treat 429, timeouts, and challenges as blockers, not semantic differences. Pivot to offline artifacts, low-frequency single-variable probes, or a different known entry point instead of repeating the probe matrix.

When does API reverse engineering stop and hand off to vulnerability testing?

Handoff occurs once evidence identifies a concrete target: object IDs go to IDOR testing, writable fields to misconfiguration checks, query-like inputs to SQLi or NoSQLi, tokens to JWT analysis, and callbacks to SSRF testing.

Why does every API probe need to change only one variable?

Single-variable probes isolate cause and effect so schema or status differences can be attributed to a specific parameter or state. Multi-variable changes make response differences uninterpretable and break the baseline comparison method.