api-recon-and-docs

Discover reachable API endpoints, schemas, and documentation across REST, GraphQL, and mobile APIs.

5|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/Yliken/ai4 --skill api-recon-and-docs-yliken
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-recon-and-docs
Source: https://github.com/Yliken/ai4/tree/main/skills/api-recon-and-docs
Command: npx skills add https://github.com/Yliken/ai4 --skill api-recon-and-docs-yliken

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

API reconnaissance and documentation review is essential to map the surface area of REST, mobile, and GraphQL APIs, enabling safer testing, verification, and exploitation planning.

Core Features & Use Cases

  • Discover reachable API entrypoints across multiple protocols (REST, GraphQL, mobile) and surface versions.
  • Extract schemas and optional/required fields, plus role-based access hints and authentication requirements.
  • Inspect documentation endpoints and OpenAPI/Swagger specs to identify hidden surfaces and undocumented parameters.

Quick Start

Enumerate the API surface by scanning common paths, then import findings for validation and planning.

Frequently Asked Questions about api-recon-and-docs

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

FAQPage Schema
How do I enumerate API endpoints and schemas for REST and GraphQL?

You can enumerate API endpoints and schemas by scanning common paths across REST, GraphQL, and mobile protocols to identify reachable entrypoints, extract optional fields, and detect authentication requirements.

What is API reconnaissance used for in application testing?

API reconnaissance is used to map the surface area of REST and GraphQL APIs for safer testing and exploitation planning by discovering undocumented parameters, hidden documentation surfaces, and version drift.

Can I detect deprecated API paths and role-based access hints?

Yes, you can detect deprecated API paths and role-based access hints by inspecting OpenAPI/Swagger specifications and extracting schema details to map the full attack surface.

How do I find undocumented parameters in OpenAPI and Swagger docs?

You find undocumented parameters by inspecting documentation endpoints and OpenAPI/Swagger specs to identify hidden surfaces and differences between documented and reachable API paths.

Does API reconnaissance work for mobile API surfaces?

Yes, API reconnaissance works across multiple protocols including mobile APIs, extracting schemas, required fields, and authentication requirements to map the complete attack surface.