Endpoint & Request Flow Mapper

Trace every request from the interface action through JavaScript, local handlers, authentication, databases, external services, responses, and the UI that consumes them.

01 Add Application Evidence
02 Trace Request Paths
03 Inspect Contracts
04 Export the Map

Application Evidence

Files remain in this browser until analysis begins

Ready

Evidence-based mapping—not simulated testing.

The Mapper inspects supplied code and plans. It does not execute the application or prove that an endpoint responds. Declared API settings remain a planned contract until implementation evidence confirms them. Remove credentials, private records, and customer data.

Application context

Request or problem to focus on

API & Model Configuration

Describe the intended request contract. Never enter an API key, token, password, or private credential.

As Needed

Provider or service

Model or deployment

Application-facing endpoint

Provider operation or upstream endpoint

HTTP method

Connection wrapper, SDK, or client

Authentication and credential handling Describe where authentication occurs—never paste the credential itself.

Request format and required fields

Expected response and errors

Configuration notes or fallback behavior

Add Application or Planning Files PHP, JavaScript, HTML, JSON, SQL, XML, YAML, Markdown, text, or .htaccess

Evidence Files

0 of 12 files · 0 KB

Add the smallest useful set of files that contains the request path.

Paste focused code or route notes Live secrets are automatically redacted when recognizable, but you should remove them before adding evidence.

Prepare
Trace
Compare
Export

Endpoint and Request Map

Routes, contracts, boundaries, risks, and correction instructions

Waiting for Evidence

Your request-flow map will appear here

Define the intended API contract, add relevant files or focused code when available, and select Map Request Flows. The result will distinguish plans, evidence, and inference.

Analysis Summary

Endpoint Map

0% Evidence Coverage

0Endpoints

0Request Flows

0Mismatches

0Path Risks

Evidence Classification

What the supplied material can and cannot prove

Confirmed in Evidence

Reasonable Inference

Missing or Unresolved

API & Model Configuration

Not established

Endpoint Inventory

Detected request destinations and handlers

Method	Path / Destination	Kind	Source	Authentication / CSRF	Status	Evidence

Endpoint & Request Flow Mapper

Endpoint and Request Map

Your request-flow map will appear here

Endpoint Map

Evidence Classification

Confirmed in Evidence

Reasonable Inference

Missing or Unresolved

API & Model Configuration

Endpoint Inventory

Request Flows

Contract Mismatches

Path and Resolution Risks

Authentication Boundaries

Open Questions

Builder Instructions

Verification Checks