x-operator-basis
`x-operator-basis` appears in the info block. Its value is a structured object. Used by 15 providers across 38 OpenAPI documents. 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.
38 occurrences
38 documents
15 providers
purpose-named
Where it appears
| Location in the document | Occurrences | |
|---|---|---|
| info | 37 | |
| root | 1 |
What its value looks like
| Value shape | Occurrences |
|---|---|
| object | 38 |
Providers publishing it
All 15.
brownhebrew-university-of-jerusalemkauking-saud-universityohio-state-universitypostechqatarqutuabuniversity-of-antwerpuniversity-of-chicagouniversity-of-floridauniversity-of-navarraupmzhejiang
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.