Data & schema semantics

x-version

`x-version` appears on operations. Its value is a string. Used by 49 providers across 56 OpenAPI documents. Observed values include `1`, `2`, `3`, `5`. 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.

951 occurrences

56 documents

49 providers

purpose-named

Where it appears

Location in the document	Occurrences
operation	922
schema	28
info	1

What its value looks like

Value shape	Occurrences
string	926
integer	25

Observed values

Sampled from the specifications, most frequent first.

1235741.0.0v1

Providers publishing it

All 49.

aemo alex-bank alinta-energy amp-bank anz australian-military-bank auswide-bank bank-first bank-of-queensland bank-of-sydney bank-of-us banksa bankwest bcu-bank bendigo-and-adelaide-bank beyond-bank defence-bank energy-queensland energyaustralia gateway-bank gc-mutual-bank great-southern-bank greater-bank hsbc-australia hume-bank ibm-quantum imb-bank ing-australia judo-bank macquarie-bank mystate-bank national-australia-bank newcastle-permanent people-first-bank pn-bank police-bank qudos-bank rabobank-australia racq-bank red-energy regional-australia-bank simply-energy sinch spotdraft suncorp-bank teachers-mutual-bank ubank unity-bank westpac

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.