Data & schema semantics · Type system

x-enum-descriptions

`x-enum-descriptions` appears on schema objects and properties. Its value is a structured object. Used by 28 providers across 61 OpenAPI documents. 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.

1372 occurrences

61 documents

28 providers

purpose-named

Where it appears

Location in the document	Occurrences
operation	31
schema	1327
parameter	14

What its value looks like

Value shape	Occurrences
string	1
object	1272
array	99

Observed values

Sampled from the specifications, most frequent first.

{'697': RhinAer, '698': VivAer}

Providers publishing it

All 28.

aerin-medical agorapulse airia apicontext appcharge barogo booking-com california-privacy-protection-agency ccpa edf-energy enable-banking folio google-admob google-search-console hm-land-registry leap line observepoint origin-energy reclaim-ai runloop-ai saxo scaleway spyfu toqio unity-catalog zerion zoho-cliq

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.