Data & schema semantics · Ordering & sorting

x-position

`x-position` appears on operations. Its value is an integer. Used by 11 providers across 36 OpenAPI documents. Observed values include `1`, `2`, `3`, `4`. Consistent with ordering & sorting — 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.
6592 occurrences
36 documents
11 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 5391
requestBody 1048
parameter 146
path 7

What its value looks like

Value shapeOccurrences
integer6592

Observed values

Sampled from the specifications, most frequent first.

12345678

Providers publishing it

All 11.

airiabullishcancer-govcloudguardcursedolbydotdigitallytxmetabolonsinchtui-group

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.