endpoint-exploration

Document undocumented REST API endpoints through empirical testing and URL analysis.

Updated Oct 25, 2025
One-click install
npx skills add https://github.com/Omegaice/claude-code-marketplace --skill endpoint-exploration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: endpoint-exploration
Source: https://github.com/Omegaice/claude-code-marketplace/tree/main/skills/endpoint-exploration
Command: npx skills add https://github.com/Omegaice/claude-code-marketplace --skill endpoint-exploration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the discovery and documentation of undocumented REST API endpoints by performing methodical URL analysis and empirical testing, reducing manual exploration time and the risk of missing edge cases.

Core Features & Use Cases

  • URL structure analysis: identify path parameters and endpoint patterns without making assumptions.
  • Parameter discovery: infer parameter types and constraints from request patterns.
  • Minimal test case generation: create concise tests to validate endpoint behavior.
  • Request execution & sampling: run deterministic curl-based requests and capture full responses for analysis.
  • Documentation generation: produce structured endpoint-documentation.md with authentication, parameters, and response schemas.
  • Use case: document undocumented APIs for integration guides, API catalogs, or reverse-engineering efforts.

Quick Start

Provide the target API URL and run the skill to begin automated URL analysis, test generation, sample collection, and documentation writing. For example, point it at https://api.example.com/v1/resource/{id} and let it generate endpoint-documentation.md based on observed responses.

Frequently Asked Questions about endpoint-exploration

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

FAQPage Schema
How do I document REST API endpoints that lack official documentation?

Systematic empirical testing automates REST API endpoint discovery by analyzing URL structures, inferring parameters, and generating minimal test cases with curl to capture responses. This reduces manual exploration time and identifies edge cases automatically.

Can I reverse-engineer API endpoints using curl-based testing?

Yes. URL structure analysis identifies path parameters and endpoint patterns, while deterministic curl requests execute against the target API to sample responses and validate behavior without assumptions about undocumented endpoints.

What's the best way to create integration documentation from API responses?

Capture full response samples from test execution, then generate structured endpoint-documentation.md containing authentication details, parameter schemas, and response formats derived from observed data patterns.

How do I identify API parameter types and constraints without source code?

Parameter discovery infers types and constraints by analyzing request patterns across test cases, extracting parameter behavior from actual API responses rather than relying on missing or incomplete API specifications.

Does this approach work for exploring undocumented third-party APIs?

Yes. Point the skill at any REST API URL and run automated analysis to generate endpoint documentation through URL analysis, test case generation, request execution, and response inspection without requiring API source code or documentation.

What are the limitations of empirical endpoint testing?

Testing relies on observable behavior and may miss endpoints not exposed through standard patterns, rate-limited endpoints, or those requiring specific authentication credentials or complex request sequences not inferred from URL structure alone.