SDK & code generation

x-go-name

`x-go-name` appears on schema objects and properties. Its value is a string. Used by 33 providers across 81 OpenAPI documents. Observed values include `Name`, `Description`, `Type`, `Id`. 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 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.
24622 occurrences
81 documents
33 providers
purpose-named

Where it appears

Location in the documentOccurrences
response 223
schema 22710
tag 74
path 2
operation 1591
parameter 19
header 3

What its value looks like

Value shapeOccurrences
string24622

Observed values

Sampled from the specifications, most frequent first.

NameDescriptionTypeIdIDJsonProfileUIDToken

Providers publishing it

All 33.

acquiaakeylessaxelarcanonicalcmscms-govcohesitydockerelastic-pathfluidstackgiteagmi-cloudhaproxyharnesshatchetincusisovalentkongkumalightspeedmadhivenacellepicus-securitypodmansakura-internetspectro-cloudsynacktiledbtvdbtykubicloudvolumezwindmill

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.