strata19.endpoint_inventory

What it does

Whole-repo HTTP endpoint inventory built from the SAME role data the framework-semantics and pack planes already compute (route registrations, middleware role bindings, accepted request schemas, direct persistence calls) — never a new analysis pass. list answers "how many endpoints, how many unauthenticated, how many take input with no validation, what tables does anything here touch". query answers a specific question against that inventory: "what writes to the users table", "which endpoints touch billing", "which endpoints have no auth binding".

When to use it

Use when: "how many API endpoints does this have" · "which endpoints are unauthenticated" · "what writes to the X table" · "which endpoints touch billing/payments/PII" · "audit my API surface" · onboarding to an unfamiliar repo's HTTP surface

Also use when: planning a schema/table change and needing to know which endpoints would be affected, or reviewing a new endpoint against the auth/validation conventions the rest of the repo already follows

When not to use it

you want ONE route's full middleware chain with store-backed caller enrichment — use strata19.project_intelligence (actions: route_context, middleware_chain) instead; or a severity-graded security/correctness finding — use the detector/finding tools (this tool never asserts something is WRONG, only what IS).

Availability