Explore APIs and code flows

Find an endpoint#

1. 1

   Open APIs

   Go to APIs. The table lists method and path, service, inferred route type, handler and source location, static callers, API request counts, attributed function calls, and retirement state.

2. 2

   Search or filter

   Use Search APIs and services to find a method, path, or service. Select a service in the filter to narrow the table; choose Clear to reset it.

3. 3

   Select the endpoint

   Choose its path to open the endpoint detail panel below the table.

Inspect endpoint details#

A source reference includes a file, line, and commit SHA. GitHub opens the recorded commit rather than the latest branch, so the evidence remains tied to the snapshot or analysis that produced it.

Route types such as UI/demo, system, and webhook are inferred from source paths and route patterns. They help separate likely interface and operational routes from application routes; they do not prove deployment or production use. Choose a handler to open its reachable function flow and call sites.

The displayed request and response schemas are extracted from supported documents. Complex or unsupported schema constructs can leave analysis incomplete. Review the repository's Coverage notes when an expected schema or endpoint is missing.

Follow static API dependencies#

1. 1

   Reindex the selected repositories

   Use Re-index in Repositories to pick up additional implemented routes and supported configured HTTP clients. Source indexing does not require Kubernetes, Prometheus or Datadog.

2. 2

   Open the provider's Code flow

   Consumer APIs and call sites lists which consumer APIs can reach the HTTP caller. Follow a consumer API to inspect its helper calls and downstream APIs. Shared functions can belong to multiple API flows.

3. 3

   Inspect source and conditions

   Source references include the indexed commit and call position. Static conditions and input origins shows supported branch predicates and symbolic handler parameter paths. It does not record actual request values or branch executions.

4. 4

   Review unresolved callers

   Static HTTP dependencies below the function inventory includes ambiguous providers and callers with no discovered enclosing API. An empty API list does not establish that the caller is unused or a background task.

Endpoint Overview distinguishes contract definitions, implemented routes, and routes supported by both. Implemented routes missing from OpenAPI remain visible with no inferred schemas. Explicit client URL origins and OpenAPI server origins can disambiguate providers; route-only matches remain possible and require identity review.

Interpret usage and confidence#

Static callers counts detected relationships in selected indexed repositories. It does not measure traffic volume or capture every deployed consumer. A relationship inferred from a unique endpoint path still requires verification of the deployment host association.