Data & schema semantics · Defaults & examples

x-default

`x-default` appears on security schemes. Its value is a string. Used by 11 providers across 13 OpenAPI documents. Observed values include `NEYNAR_API_DOCS`, `default`, `Bearer token`, `your_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.
14 occurrences
13 documents
11 providers
purpose-named

Where it appears

Location in the documentOccurrences
securityScheme 14

What its value looks like

Value shapeOccurrences
string14

Observed values

Sampled from the specifications, most frequent first.

NEYNAR_API_DOCSdefaultBearer tokenyour_api_keyDevKey11111111-1111-1111-1111-111111111111Bearer qhtfs87hjnc12kkos

Providers publishing it

All 11.

bluecoreclerk-ioheygennewswhipneynarrariblescalapaysmtp2gotogether-aiviglinkxeneta

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.