x-bundled-from

`x-bundled-from` appears at the root of the document. Its value is a string. Used by 2 providers across 11 OpenAPI documents. Observed values include `https://github.com/openmobilityfoundation/mds-openapi/blob/v2.0/reference/agency`, `https://github.com/openmobilityfoundation/mds-openapi/blob/v2.0/reference/geogra`, `https://github.com/openmobilityfoundation/mds-openapi/blob/v2.0/reference/jurisd`, `https://github.com/openmobilityfoundation/mds-openapi/blob/v2.0/reference/metric`. 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.
11 occurrences
11 documents
2 providers
purpose-named

Where it appears

Location in the documentOccurrences
root 11

What its value looks like

Value shapeOccurrences
string11

Observed values

Sampled from the specifications, most frequent first.

https://github.com/openmobilityfoundation/mds-openapi/blob/v2.0/reference/agencyhttps://github.com/openmobilityfoundation/mds-openapi/blob/v2.0/reference/geograhttps://github.com/openmobilityfoundation/mds-openapi/blob/v2.0/reference/jurisdhttps://github.com/openmobilityfoundation/mds-openapi/blob/v2.0/reference/metrichttps://github.com/openmobilityfoundation/mds-openapi/blob/v2.0/reference/policyhttps://github.com/openmobilityfoundation/mds-openapi/blob/v2.0/reference/providopenapi/_original/stitch-capture-services/auth-services-v1.0.yaml (./models refsopenapi/_original/stitch-capture-services/capture-services-v1.0.yaml (./models r

Providers publishing it

All 2.

open-mobility-foundationspliceforms

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.