Data & schema semantics

x-audience

`x-audience` appears on operations. Its value is a string. Used by 19 providers across 44 OpenAPI documents. Observed values include `public`, `external-public`, `external-partner`, `external-merchant`. 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.
206 occurrences
44 documents
19 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 40
schema 1
server 1
tag 5
path 16
operation 143

What its value looks like

Value shapeOccurrences
string205
object1

Observed values

Sampled from the specifications, most frequent first.

publicexternal-publicexternal-partnerexternal-merchantEXpartnerexternalcompany-internal

Providers publishing it

All 19.

argyleceloniscoalescecommusoftdocker-hubfabric-comlmntmicrosoft-azure-active-directorymicrosoft-outlookpalo-alto-networksquinyxreflektiveregal-entertainment-groupregions-financialsap-concursmokeballzalandozallyzestful

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.