Documentation & DX

x-order

`x-order` appears on schema objects and properties. Its value is an integer. Used by 12 providers across 19 OpenAPI documents. Observed values include `0`, `1`, `2`, `3`. Consistent with documentation & dx — this is inferred from where the key appears and what it carries, not from any published definition.

Documentation & DX 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.
10763 occurrences
19 documents
12 providers
purpose-named

Where it appears

Location in the documentOccurrences
schema 10339
other 4
server 6
tag 8
operation 406

What its value looks like

Value shapeOccurrences
string340
integer10418
number5

Observed values

Sampled from the specifications, most frequent first.

01234567

Providers publishing it

All 12.

altrbakktbolt-financialbungalowcohesitydescopeform3gameyeharnessmagic-edennalaspectro-cloud

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 documentation & dx job.