Data & schema semantics · Identity & relationships

x-api-id

`x-api-id` appears in the info block. Its value is a string. Used by 42 providers across 107 OpenAPI documents. Observed values include `TMF931`, `sap-concur-expense-report-v4`, `5ca54741-8f62-4aad-ab79-13ae762920e3`, `96f61af0-7bba-45df-8f12-005042cf1e47`. Consistent with identity & relationships — 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.

108 occurrences

107 documents

42 providers

purpose-named

Where it appears

Location in the document	Occurrences
info	108

What its value looks like

Value shape	Occurrences
string	107
object	1

Observed values

Sampled from the specifications, most frequent first.

TMF931sap-concur-expense-report-v45ca54741-8f62-4aad-ab79-13ae762920e396f61af0-7bba-45df-8f12-005042cf1e470a0913f4-76e3-4a84-8560-b09aa65823e946234552-5833-42eb-ba0f-883ad3f70d2bexchangerate:exchangerate-api38254dbd-d8fe-44cb-b1d6-4508cf74fd50

Providers publishing it

All 42.

acuant aeris argyle bazaarvoice bigml coalesce commusoft concur confluent confluent-the-data-streaming-platform exchangerate-api forex-com fueleconomy glitchtip gridx-ai gsma jaggaer lmnt microsoft-defender microsoft-outlook open-gateway pagopa patch-io penpot reflektive regal-entertainment-group regions-financial regulations-gov sap-concur simon-data small-improvements smartlook smokeball solar-edge taxjar tines valueserp verdaccio widen zalando zally zestful

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.