Explore APIs and OpenAPI contracts

Three different kinds of API evidence

• Incoming: supported handler or provider definitions found in source.

• Outgoing: supported client calls found in source.

• Declaration: operations described by an indexed OpenAPI contract. A declaration alone is not proof of a deployed handler.

Find an endpoint

1. Open an indexed workspace and choose API & DB, then APIs in code.

2. Use the role filter to distinguish Outgoing, Handler declaration and Registration. Identify the method, route/protocol and owning source. Open an OpenAPI source separately to inspect its declared operations.

3. Open an item and inspect its details and evidence. Follow the code action to the implementation or the declaration action to its contract.

4. Use callers/callees or nearby code relationships for the owning symbol when available. Keep direction and relation type explicit.

5. Read partial/unresolved notices and pagination before describing the result as complete.

Read an OpenAPI contract

Select an indexed OpenAPI JSON or YAML source from the declarations list. Explorer reads OpenAPI 3.0 and 3.1 operations and bounded parameter, request-body, response and schema summaries. Source pointers lead back to the original document. Same-document references are bounded; external references are not fetched.

Boundary relationships

Supported static HTTP relationships can connect a recognizable consumer and provider when their identities match uniquely. Tauri IPC, generated-style Go/Java/.NET gRPC and named Python Celery tasks have their own boundary evidence. These are distinct from ordinary function calls; a matching label is not sufficient to invent a cross-language call.

What is not established

• No request is sent to an endpoint, and no server availability, authentication policy or response behavior is tested.

• Dynamic URLs, runtime routing, middleware, dependency injection and generated behavior can remain partial.

• OpenAPI callbacks/webhooks, external reference resolution, Python gRPC and a general standalone Protocol Buffers analyzer are not claimed.

• GraphQL and arbitrary API frameworks are not advertised as supported merely because their source files are indexed.

Ask a connected agent

Ask for the endpoint’s role, owning symbol, source pointer or range and indexed revision. The agent can use get_api_catalog and get_openapi_contract. Then read the implementation and run the appropriate tests in your own project; an API graph does not run them.

If the view is missing or empty

Check the installed Explorer version, selected workspace, indexing result and supported declaration format. Empty, unsupported and failed results have different meanings. Refresh the index after changing routes or contracts before combining old and new observations.