Runtime & gateway

x-swagger-router-controller

`x-swagger-router-controller` appears on operations. Its value is a string. Used by 4 providers across 6 OpenAPI documents. It sits in the `x-swagger-` namespace, so its meaning is defined by swagger tooling rather than by OpenAPI. Observed values include `api.resource`, `api.screen`, `Data`, `api.session`. Consistent with runtime & gateway — this is inferred from where the key appears and what it carries, not from any published definition.

Runtime & gateway x-swagger- namespace derived description
How this description was produced. It is assembled from what was measured in the corpus — where this key appears in a document, what shape its value takes, the values observed, and how many providers use it. It is not taken from a published definition, because for most extensions none exists. Read it as evidence, not as a specification. If you own this extension and want it described properly, tell us.
223 occurrences
6 documents
4 providers
vendor-named

Where it appears

Location in the documentOccurrences
operation 188
path 35

What its value looks like

Value shapeOccurrences
string223

Observed values

Sampled from the specifications, most frequent first.

api.resourceapi.screenDataapi.sessionapi.applicationInformationapi.queryReferencesGroups

Providers publishing it

All 4.

adafruit-iomercedes-metricentisuniversity-of-chicago

Why this is not in OpenAPI

Extensions exist because a provider needed something the specification would not carry. Most of what they hold is not the API contract at all — it is operational metadata about the contract: documentation, lifecycle, policy, provenance, and now agents. That metadata is usually better placed alongside the contract, in an Overlay or an APIs.json index, than crammed inside it. See everything else doing the runtime & gateway job.