Data & schema semantics · Type system

x-enumDescriptions

`x-enumDescriptions` appears on schema objects and properties. Its value is a list. Used by 22 providers across 52 OpenAPI documents. Observed values include `*ref_91`, `&ref_91`. Consistent with type system — 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.
927 occurrences
52 documents
22 providers
purpose-named

Where it appears

Location in the documentOccurrences
schema 855
parameter 15
operation 57

What its value looks like

Value shapeOccurrences
string3
object263
array661

Observed values

Sampled from the specifications, most frequent first.

*ref_91&ref_91

Providers publishing it

All 22.

ankorstorebonitasoftbullishcontrolupdassaultdropboxelastic-pathhellosignhetznerland-insightmewsmews-commews-systemsripple-labsshipmonksnow-softwarespyfuvalhallaveeamweavrwiseworldpay

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.