Data & schema semantics

x-status

`x-status` appears in the info block and on operations. Its value is a string. Used by 27 providers across 76 OpenAPI documents. Observed values include `validated`, `modeled`, `Work in progress`, `STABLE`. 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.
107 occurrences
76 documents
27 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 72
operation 33
server 2

What its value looks like

Value shapeOccurrences
string105
object2

Observed values

Sampled from the specifications, most frequent first.

validatedmodeledWork in progressSTABLEretireddeprecatedconfirmedDEVELOPMENT

Providers publishing it

All 27.

aboundamadeusamadeus-reservationsamadeus-solutionsamadeus-traveler-mediablockchalkboredelhubflowdockjservicemyfatoorahokra-ngopenehrpassbaseplacekittenpunkapiricerocksolidromitron-swanson-quotessegmentsila-moneytd-ameritrade-holdingtradifytvarkavivalinkwestern-alliance-bancorporation

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.