x-speakeasy-name-override
`x-speakeasy-name-override` appears on operations and on schema objects and properties. Its value is a string. Used by 29 providers across 60 OpenAPI documents. It sits in the `x-speakeasy-` namespace, so its meaning is defined by speakeasy tooling rather than by OpenAPI. Observed values include `get`, `list`, `create`, `data`. Consistent with sdk & code generation — 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 | 28 | |
| operation | 2759 | |
| schema | 1627 | |
| root | 3 | |
| response | 125 |
What its value looks like
| Value shape | Occurrences |
|---|---|
| string | 4537 |
| array | 3 |
| object | 2 |
Observed values
Sampled from the specifications, most frequent first.
Providers publishing it
All 29.
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.