Documentation & DX

x-display-name

`x-display-name` appears on schema objects and properties. Its value is a string. Used by 8 providers across 35 OpenAPI documents. Observed values include `Api collection `1`, `participants`, `splits`, `Problem details`. 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.
2077 occurrences
35 documents
8 providers
purpose-named

Where it appears

Location in the documentOccurrences
schema 1983
other 87
root 2
operation 5

What its value looks like

Value shapeOccurrences
string2075
object2

Observed values

Sampled from the specifications, most frequent first.

Api collection `1participantssplitsProblem detailsConditionCondition Testsitescampaigns

Providers publishing it

All 8.

blackbaudbooking-comclouderaemnifyexoscalehaproxyperfect-corpsociallisteningapi

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.