The specification nobody wrote down.
Every flow, fused into one list of endpoints, then exported.
From traffic to a spec
Read the surface, then export it.
apiaxess
Go to surface, flow, endpoint or command⌘K
api.northwind-retail.ioLive control connected
Merged · 128 endpoints · both clients
API surface
Every endpoint below is backed by evidence. Confidence is the weakest fact supporting it, and coverage states plainly what remains unconfirmed.
Export artifacts
MethodPathClientsSamplesConfidenceStatus
GET/v1/mewebapp214high● 200 · 41ms
GET/v1/cartwebapp188high● 200 · 22ms
POST/v1/cart/itemswebapp96high● 201 · 53ms
GET/v1/checkout/quoteapp31medium● 500 · 612ms
POST/v1/checkout/confirmapp12medium● 201 · 88ms
POST/v1/push/registerapp9high● 200 · 18ms
GET/v1/loyalty/pointsapp44high● 200 · 27ms
PATCH/v1/me/preferencesapp6low● 200 · 38ms
GET/v1/internal/flagsweb3low● 403 · 19ms
Intercept queue 0Diagnostics 0Control · reliable
No paused requestsWith intercept on, matching requests pause here until you forward, modify or drop them.
API SURFACEsession:2l1a434f3f6b1aControlTelemetry127.0.0.1
Browser, device, APK and imported HAR fused into one list.
The details
- Formats
- OpenAPI 3.1, Postman v2.1, HAR 1.2 and a Python httpx client ·
--format openapi | sdk | postman | har | all - Evidence
- Each field carries its confidence and provenance; an
apiaxess-evidence.jsonsidecar ships alongside - Import
- HAR goes back in, classified against scope
$ apiaxess export ./session.json --format all --out ./out
The control-plane API is internal
It may change between builds. Script the CLI instead:
analyze, web, inspect and export all take --json.