Data & schema semantics · Type system

x-type-name

`x-type-name` appears on schema objects and properties and on parameter objects. Its value is a string. Used by a single provider across 16 OpenAPI documents. Observed values include `UtcDateTime`, `Date`, `AccountKey`, `ClientKey`. 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.
561 occurrences
16 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
parameter 236
schema 325

What its value looks like

Value shapeOccurrences
string561

Observed values

Sampled from the specifications, most frequent first.

UtcDateTimeDateAccountKeyClientKeyAccountGroupKeyClientIdUicCurrencyCode

Providers publishing it

All 1.

saxo

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.