Data & schema semantics · Type system

x-go-type

`x-go-type` appears on schema objects and properties. Its value is a string. Used by 34 providers across 45 OpenAPI documents. Observed values include `float64`, `uuid.UUID`, `int64`, `string`. Consistent with type system — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics 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.
388 occurrences
45 documents
34 providers
purpose-named

Where it appears

Location in the documentOccurrences
schema 363
parameter 14
requestBody 3
operation 7
tag 1

What its value looks like

Value shapeOccurrences
string353
object35

Observed values

Sampled from the specifications, most frequent first.

float64uuid.UUIDint64stringnet/netip.Addrinterface{}net.IPpaymentgateways.GatewayName

Providers publishing it

All 34.

airmdranchorageankorstoreaxelarbinarlyblockdaemonconfluentconfluent-the-data-streaming-platformdailypaydockerelastic-pathexoscaleflatcar-container-linuxgmi-cloudharnesshatchetisovalentkernelkongkumalaunchdarklylightspeedmomentnhostnucleiopal-securityoraclepodmanpolygon-idscope3sumuptiledbvenafixata

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 data & schema semantics job.