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.
Where it appears
| Location in the document | Occurrences | |
|---|---|---|
| root | 11 |
What its value looks like
| Value shape | Occurrences |
|---|---|
| string | 11 |
Observed values
Sampled from the specifications, most frequent first.
Providers publishing it
All 2.
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.