Data & schema semantics · Type system

x-extensible-enum

`x-extensible-enum` appears on schema objects and properties. Its value is a list. Used by 16 providers across 55 OpenAPI documents. Observed values include `[AWS, GCP, AZURE]`, `[ZIP, JAR]`, `[ORGANIZATION, ENVIRONMENT, CLUSTER, CONNECTOR,`, `[AWS]`. 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.
1868 occurrences
55 documents
16 providers
purpose-named

Where it appears

Location in the documentOccurrences
schema 1819
parameter 30
response 18
operation 1

What its value looks like

Value shapeOccurrences
array1864
boolean4

Observed values

Sampled from the specifications, most frequent first.

[AWS, GCP, AZURE][ZIP, JAR][ORGANIZATION, ENVIRONMENT, CLUSTER, CONNECTOR,[AWS][aws, azure, gcp][ESSENTIALS, ADVANCED][PROVISIONING, PROVISIONED, FAILED][PRESIGNED_URL_LOCATION]

Providers publishing it

All 16.

8x8aerisapis-iobazaarvoicebirdconfluentconfluent-the-data-streaming-platformduvo-aieu-sovereign-cloud-apigridx-aiharnessinterhyppagopauniversity-of-manchesterzalandozally

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.