Data & schema semantics · Naming & aliasing

x-ibm-name

`x-ibm-name` appears in the info block. Its value is a string. Used by 5 providers across 153 OpenAPI documents. It sits in the `x-ibm-` namespace, so its meaning is defined by ibm tooling rather than by OpenAPI. Observed values include `product-management-api`, `accounts`, `aces-order-approval`, `paymentservices`. 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-ibm- 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.
166 occurrences
153 documents
5 providers
vendor-named

Where it appears

Location in the documentOccurrences
info 160
schema 6

What its value looks like

Value shapeOccurrences
string160
object6

Observed values

Sampled from the specifications, most frequent first.

product-management-apiaccountsaces-order-approvalpaymentservicesvca-life-cycle-managementvca-reportingauthenticationservicesv2patientaccessallergyintoleranceid

Providers publishing it

All 5.

acousticaetnaciticitizens-financial-groupibm-api-connect

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.