Data & schema semantics · Defaults & examples

x-default

`x-default` appears on security schemes. Its value is a string. Used by 27 providers across 67 OpenAPI documents. Observed values include `auth_token`, `null`, `SALSIFY_TOKEN`, `API_KEY`. Consistent with defaults & examples — 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.
76 occurrences
67 documents
27 providers
purpose-named

Where it appears

Location in the documentOccurrences
securityScheme 64
schema 10
other 2

What its value looks like

Value shapeOccurrences
string76

Observed values

Sampled from the specifications, most frequent first.

auth_tokennullSALSIFY_TOKENAPI_KEY5evddf6604d2845b3b27023e5c2716f1your_api_keyBearer instill_sk_***XXXXXXXXXX

Providers publishing it

All 27.

alkemicsamberdataayla-networksbluecoreclerk-ioclouderadynamic-yieldfeedlyheygenhumanityinscribeinstill-ailoudcrowdmoodys-rmsnetcorecloudnewswhipneynaropen-financialperkrariblescalapaysmtp2gosovrntogether-aiviglinkworkrampxeneta

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.