x-internal
`x-internal` appears on schema objects and properties. Its value is a boolean flag. Used by 65 providers across 165 OpenAPI documents. Consistent with visibility — 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 | |
|---|---|---|
| schema | 1370 | |
| operation | 473 | |
| path | 26 | |
| info | 1 | |
| response | 1 | |
| requestBody | 1 | |
| server | 2 | |
| root | 29 | |
| other | 3 | |
| parameter | 6 | |
| components | 2 | |
| tag | 4 |
What its value looks like
| Value shape | Occurrences |
|---|---|
| boolean | 1913 |
| string | 5 |
Observed values
Sampled from the specifications, most frequent first.
Providers publishing it
Showing 50 of 65.
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 visibility job.