Runtime & gateway

x-openapi-router-controller

`x-openapi-router-controller` appears on operations. Its value is a string. Used by 5 providers across 5 OpenAPI documents. Observed values include `app.controllers.project_controller`, `app.controllers.company_controller`, `app.controllers.analytics_controller`, `athenian.api.controllers.settings_controller`. Consistent with runtime & gateway — this is inferred from where the key appears and what it carries, not from any published definition.

Runtime & gateway 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.
366 occurrences
5 documents
5 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 366

What its value looks like

Value shapeOccurrences
string366

Observed values

Sampled from the specifications, most frequent first.

app.controllers.project_controllerapp.controllers.company_controllerapp.controllers.analytics_controllerathenian.api.controllers.settings_controllerapp.controllers.datapoint_controllerathenian.api.controllers.filter_controllerapp.controllers.controls_controllerapp.controllers.user_controller

Providers publishing it

All 5.

aedifionapache-airflowathenianenterprisedbsp-global

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.