Data & schema semantics

x-operator

`x-operator` appears in the info block. Its value is a string. Used by 106 providers across 319 OpenAPI documents. Observed values include `institution`, `tenant`, `institution — every host is under IIT Delhi's own registrable domain`. 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.

322 occurrences

319 documents

106 providers

purpose-named

Where it appears

Location in the document	Occurrences
info	221
root	81
other	18
server	2

What its value looks like

Value shape	Occurrences
string	322

Observed values

Sampled from the specifications, most frequent first.

institutiontenantinstitution — every host is under IIT Delhi's own registrable domain

Providers publishing it

Showing 50 of 106.

anu boston brown caltech carnegie-mellon-university columbia cornell curtin dartmouth epfl fudan georgia-institute-of-technology hanyang harvard hebrew-university-of-jerusalem hku hkust humboldt-universitat-zu-berlin iit-delhi iit-kanpur imperial-college-london kau keio khalifa king-saud-university ku-leuven kyoto kyushu lse maastricht macquarie massey mcgill mcmaster ntu nycu ohio-state-university peking politecnico-di-milano politecnico-di-torino postech princeton qatar qut rice shanghai-jiao-tong-university snu texas-a-m-university tokyo-institute-of-technology tongji

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.