Data & schema semantics · Naming & aliasing

x-bump-branch-name

`x-bump-branch-name` appears in the document. Its value is a string. Used by a single provider across 1 OpenAPI document. It sits in the `x-bump-` namespace, so its meaning is defined by bump tooling rather than by OpenAPI. Observed values include `demo`, `prod`. Consistent with naming & aliasing — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics x-bump- namespace 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.

2 occurrences

1 documents

1 providers

vendor-named

Where it appears

Location in the document	Occurrences
other	2

What its value looks like

Value shape	Occurrences
string	2

Observed values

Sampled from the specifications, most frequent first.

demoprod

Providers publishing it

All 1.

lightspeed-pos

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.