ASP.NET endpoints in the HTTP tab

The HTTP tab merges Wolverine HTTP chains and non-Wolverine ASP.NET Core endpoints into a single table — one row per endpoint, with a Source chip telling you what kind of endpoint each row is.

What the Source chip means

Source	What it is
Wolverine	A Wolverine HTTP chain (handler discovered by MapWolverineEndpoints())
MinimalApi	A Minimal API endpoint (app.MapGet, app.MapPost, app.MapHub-like delegates)
Mvc	An MVC controller action — one row per action, not per controller
RazorPages	A Razor Pages handler
SignalR	A SignalR hub method
StaticFile	A static-file fallthrough endpoint (no HTTP method metadata)
Other	A route mapped via something CritterWatch doesn't have a discriminator for yet

Wolverine HTTP chains always come back in the table; non-Wolverine endpoints only appear when the host opted into the integration package by calling services.AddCritterWatchHttp(). Pure-Wolverine workers and console hosts that don't reference an ASP.NET Core stack pay zero cost — no extra package reference, no extra endpoint walk.

How to read the table

• Filter chips — click a Source chip to narrow the table to that source. Click again to release the filter. Combine multiple chips to inspect, say, Wolverine + MinimalApi in one go.
• Filter input — substring match across route, method set, and handler name.
• Click a row — drill into the appropriate detail page:
  • Wolverine rows go to the HTTP chain detail page, which surfaces full per-chain detail including generated code, the OpenAPI shape, and the middleware pipeline.
  • Non-Wolverine rows go to the ASP.NET endpoint detail page (a trimmed sister page — Overview + OpenAPI only).

OpenAPI coverage

Endpoints that ASP.NET Core's API Explorer knows about (Minimal API + MVC controllers) get their full OpenAPI shape — parameters, request bodies, response schemas, security — surfaced on the OpenAPI tab of the detail page. Endpoints API Explorer doesn't see (notably SignalR hubs) appear in the table with a Source chip but their detail page reports "No OpenAPI metadata captured" — the route is exposed, but the wire shape is not introspectable from outside the hub itself.

If the host opts into Microsoft.AspNetCore.OpenApi's document service, the descriptors get richer schemas with full $ref resolution. Swashbuckle is never required and never referenced.

Authorization

The detail page surfaces [Authorize] policies and roles for non-Wolverine endpoints under "Authorization". When the OpenAPI document carries a security scheme, the OpenAPI tab also lists scope requirements per scheme.