SDK & code generation

x-ms-client-name

`x-ms-client-name` appears on header objects and on parameter objects. Its value is a string. Used by 7 providers across 147 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tooling rather than by OpenAPI. Observed values include `ErrorCode`, `Version`, `RequestId`, `ClientRequestId`. Consistent with sdk & code generation — this is inferred from where the key appears and what it carries, not from any published definition.

SDK & code generation x-ms- namespace 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.
3616 occurrences
147 documents
7 providers
vendor-named

Where it appears

Location in the documentOccurrences
schema 992
parameter 1300
header 1323
tag 1

What its value looks like

Value shapeOccurrences
string3616

Observed values

Sampled from the specifications, most frequent first.

ErrorCodeVersionRequestIdClientRequestIdclientRequestIdreturnClientRequestIdocpdateifMatch

Providers publishing it

All 7.

azure-container-registryazure-function-appsazure-functionsazure-storage-accountazure-storage-accountsengineering-platformmicrosoft-azure

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.