Data & schema semantics

x-audience

`x-audience` appears on server objects and on operations. Its value is a string. Used by 27 providers across 102 OpenAPI documents. Observed values include `business-unit-internal`, `public`, `external-public`, `external-partner`. Consistent with data & schema semantics — 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.

513 occurrences

102 documents

27 providers

purpose-named

Where it appears

Location in the document	Occurrences
info	98
schema	56
server	175
tag	5
path	16
other	5
operation	158

What its value looks like

Value shape	Occurrences
string	435
object	2
array	76

Observed values

Sampled from the specifications, most frequent first.

business-unit-internalpublicexternal-publicexternal-partnervelocityexternal-merchantEXpartner

Providers publishing it

All 27.

aeris argyle bazaarvoice celonis coalesce commusoft concur confluent confluent-the-data-streaming-platform docker-hub fabric-com gridx-ai icontainers lmnt microsoft-outlook pagopa palo-alto-networks quinyx reflektive regal-entertainment-group regions-financial sap-concur showpad smokeball 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.