Data & schema semantics · Type system

x-enumDescriptions

`x-enumDescriptions` appears on schema objects and properties. Its value is a list. Used by 36 providers across 84 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.

2809 occurrences

84 documents

36 providers

purpose-named

Where it appears

Location in the document	Occurrences
schema	2600
parameter	117
operation	90
path	2

What its value looks like

Value shape	Occurrences
string	3
object	1253
array	1553

Observed values

Sampled from the specifications, most frequent first.

*ref_91&ref_91

Providers publishing it

All 36.

ankorstore bonitasoft booking-com bullish controlup dailypay dassault delta-exchange doit doordash drata dropbox elastic-path google-ads google-analytics-4 google-dialogflow hellosign hetzner instantly-ai land-insight mews-com okta openai perfect-corp ripple-labs security-scorecard shipmonk sinch snow-software spyfu stotles valhalla veeam weavr wise worldpay

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.