api-endpoint-mapper

Map API endpoints across codebases to reveal backend definitions and frontend calls.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/Maxcogar/agent-armory --skill api-endpoint-mapper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-endpoint-mapper
Source: https://github.com/Maxcogar/agent-armory/tree/main/skills/api-endpoint-mapper
Command: npx skills add https://github.com/Maxcogar/agent-armory --skill api-endpoint-mapper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and map every API endpoint defined in the project against every API call made from the frontend, so you can see which routes exist, which are unused, and where mismatches or typos break data flows.

Core Features & Use Cases

  • Backend endpoint discovery (Express routes, Next.js API routes) and frontend calls (fetch, axios, custom clients) to build a comprehensive map.
  • Detect unmatched calls, unused endpoints, and potential typos to speed debugging and refactoring.
  • Generate a structured report (e.g., API Endpoint Report) for sharing with teammates or feeding into CI/CD.

Quick Start

Run the endpoint scanner on your project to generate API-ENDPOINT-REPORT.md in the project root.

Frequently Asked Questions about api-endpoint-mapper

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

FAQPage Schema
How do I map API endpoints across a full-stack codebase to find frontend and backend mismatches?

Mapping API endpoints across a full-stack codebase reveals backend definitions, frontend calls, and their connections to identify unmatched calls, unused endpoints, and typos that break data flows.

What is the best way to detect unused Express routes and unmatched fetch calls during a refactor?

Detecting unused Express routes and unmatched fetch calls requires analyzing backend definitions against frontend calls to generate a consolidated report highlighting missing mappings and potential typos.

Can I audit Next.js API routes and WebSocket endpoints in a monorepo?

Auditing Next.js API routes and WebSocket endpoints in a monorepo is supported by analyzing common route patterns and frontend clients to build a comprehensive map of all connections.

How do I generate an API endpoint report for debugging and CI/CD integration?

Generating an API endpoint report involves scanning your project to output a structured markdown file in the project root, which can be shared with teammates or fed into CI/CD pipelines.

Why does my frontend axios call fail to match a backend endpoint definition?

Frontend axios calls fail to match backend endpoint definitions due to missing mappings or likely typos in the codebase, which an endpoint scanner detects by comparing call patterns against route definitions.