x-omitempty

`x-omitempty` appears on schema objects and properties. Its value is a boolean flag. Used by 27 providers across 40 OpenAPI documents. Consistent with sdk & code generation — this is inferred from where the key appears and what it carries, not from any published definition.

SDK & code generation 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.
2241 occurrences
40 documents
27 providers
purpose-named

Where it appears

Location in the documentOccurrences
schema 2176
operation 8
tag 23
server 1
header 1
response 31
parameter 1

What its value looks like

Value shapeOccurrences
boolean2237
string4

Observed values

Sampled from the specifications, most frequent first.

truefalsetru

Providers publishing it

All 27.

anchorageapiclarityaptibleatlaraxelarcleverclouderacohesitydockerelastic-pathform3goharborhaproxyharnesskalshimadhivemagic-momentmoloconalaorumpodmanpolygon-idsignadotspectro-cloudtiledbvantage-shvolumez

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 sdk & code generation job.