Data & schema semantics

x-framework-version

`x-framework-version` appears in the info block. Its value is a string. Used by a single provider across 17 OpenAPI documents. Observed values include `43.0.5+65c0bdc8ab`, `41.0.17+46f32c3eb1`, `43.0.9+b005aba300`, `38.0.2+439c5b0ec3`. Consistent with data & schema semantics — 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.
17 occurrences
17 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 17

What its value looks like

Value shapeOccurrences
string17

Observed values

Sampled from the specifications, most frequent first.

43.0.5+65c0bdc8ab41.0.17+46f32c3eb143.0.9+b005aba30038.0.2+439c5b0ec341.0.16+ebca281e1f40.0.6+1b67a0140e40.0.1+2386a0aaff37.0.4+b9d872a2f3

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.