Data & schema semantics · Naming & aliasing

x-providerName

`x-providerName` appears in the info block. Its value is a string. Used by 122 providers across 414 OpenAPI documents. Observed values include `amazonaws.com`, `googleapis.com`, `azure.com`, `Qlik`. Consistent with naming & aliasing — 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.
416 occurrences
414 documents
122 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 416

What its value looks like

Value shapeOccurrences
string416

Observed values

Sampled from the specifications, most frequent first.

amazonaws.comgoogleapis.comazure.comQlikmercedes-benz.commicrosoft.comspeechmaticsnytimes.com

Providers publishing it

Showing 50 of 122.

adscrawlamazon-app-meshamazon-app-runneramazon-codeartifactamazon-codebuildamazon-codecatalystamazon-codedeployamazon-codeguru-profileramazon-codeguru-revieweramazon-codeguru-securityamazon-codepipelineamazon-codestaramazon-cognitoamazon-comprehendamazon-compute-optimizeramazon-configamazon-device-farmamazon-devops-guruamazon-direct-connectamazon-directory-serviceamazon-dmsamazon-ec2-auto-scalingamazon-ec2-image-builderamazon-elastic-transcoderamazon-entity-resolutionamazon-eventbridge-pipesamazon-eventbridge-scheduleramazon-gameliftamazon-global-acceleratoramazon-glueamazon-glue-databrewamazon-ground-stationamazon-guarddutyamazon-health-dashboardamazon-healthimagingamazon-healthlakeamazon-healthomicsamazon-iam-access-analyzeramazon-iam-identity-centeramazon-incident-manageramazon-inspectoramazon-interactive-video-serviceamazon-iot-coreamazon-iot-device-defenderamazon-iot-device-managementamazon-iot-eventsamazon-iot-fleetwiseamazon-iot-greengrassamazon-iot-sitewiseamazon-iot-twinmaker

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.