Data & schema semantics

x-controller

`x-controller` appears on operations. Its value is a string. Used by 2 providers across 2 OpenAPI documents. Observed values include `api/comments`, `api/company_ssp_duty_assignment_matrix_duties`, `api/company_ssp_duty_assignment_matrix_roles`, `api/company_ssp_policies`. Consistent with data & schema semantics — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics 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.
130 occurrences
2 documents
2 providers
purpose-named

Where it appears

Location in the documentOccurrences
other 18
operation 112

What its value looks like

Value shapeOccurrences
string130

Observed values

Sampled from the specifications, most frequent first.

api/commentsapi/company_ssp_duty_assignment_matrix_dutiesapi/company_ssp_duty_assignment_matrix_rolesapi/company_ssp_policiesapi/company_ssp_vendorsapi/poam_itemsapi/company_ssp_duty_assignment_matrix_assignmentsapi/company_tests

Providers publishing it

All 2.

rariblesecureframe

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 data & schema semantics job.