x-example
`x-example` appears on operations and on schema objects and properties. Its value is a string. Used by 28 providers across 162 OpenAPI documents. Observed values include `true`, `1`, `POST /20160918/autonomousDatabases/<autonomousDatabaseId>/actio`, `my-company`. Consistent with mocking & testing — 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 | |
|---|---|---|
| parameter | 300 | |
| schema | 1646 | |
| operation | 3041 | |
| securityScheme | 5 | |
| header | 1 | |
| response | 11 | |
| requestBody | 1 | |
| path | 28 | |
| other | 14 | |
| tag | 3 |
What its value looks like
| Value shape | Occurrences |
|---|---|
| string | 4711 |
| integer | 82 |
| object | 32 |
| number | 34 |
| boolean | 40 |
| empty | 2 |
| array | 149 |
Observed values
Sampled from the specifications, most frequent first.
Providers publishing it
All 28.
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 mocking & testing job.