x-deprecated
`x-deprecated` appears on schema objects and properties. Its value is a boolean flag. Used by 15 providers across 19 OpenAPI documents. Consistent with change management — this is inferred from where the key appears and what it carries, not from any published definition.
Where it appears
| Location in the document | Occurrences | |
|---|---|---|
| info | 3 | |
| schema | 138 |
What its value looks like
| Value shape | Occurrences |
|---|---|
| string | 1 |
| boolean | 126 |
| array | 14 |
Observed values
Sampled from the specifications, most frequent first.
Providers publishing it
All 15.
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 change management job.