Data & schema semantics

x-operator

`x-operator` appears in the info block and at the root of the document. Its value is a string. Used by 29 providers across 60 OpenAPI documents. Observed values include `institution`, `tenant`. 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.

60 occurrences

60 documents

29 providers

purpose-named

Where it appears

Location in the document	Occurrences
info	37
root	18
other	3
server	2

What its value looks like

Value shape	Occurrences
string	60

Observed values

Sampled from the specifications, most frequent first.

institutiontenant

Providers publishing it

All 29.

anu caltech carnegie-mellon-university columbia epfl hku imperial-college-london ku-leuven kyoto lse ntu nus peking princeton snu tu-delft ubc ucsf university-of-chicago university-of-edinburgh university-of-melbourne university-of-michigan-ann-arbor university-of-oxford university-of-pennsylvania university-of-tokyo university-of-toronto university-of-wisconsin-madison unsw-sydney zhejiang

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.