Documentation & DX

x-entitlement

`x-entitlement` appears on operations. Its value is a string. Used by a single provider across 18 OpenAPI documents. Observed values include `DFX`, `CDP_DATA_SHARE_ADMIN`, `CDP_PRIVATELINKS`, `DFX_PROJECTS`. Consistent with documentation & dx — this is inferred from where the key appears and what it carries, not from any published definition.

Documentation & DX 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.
226 occurrences
18 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 222
schema 4

What its value looks like

Value shapeOccurrences
string226

Observed values

Sampled from the specifications, most frequent first.

DFXCDP_DATA_SHARE_ADMINCDP_PRIVATELINKSDFX_PROJECTSCOMPUTE_API_LIFTIEDATA_CATALOG_ENABLE_API_SERVICEAUDIT_ARCHIVING_APICORE_SRV_ON_PRIVATE_CLOUD

Providers publishing it

All 1.

cloudera

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 documentation & dx job.