Mocking & testing

x-speakeasy-example

`x-speakeasy-example` appears on security schemes. Its value is a string. Used by 3 providers across 3 OpenAPI documents. It sits in the `x-speakeasy-` namespace, so its meaning is defined by speakeasy tooling rather than by OpenAPI. Observed values include `DUB_API_KEY`, `YOUR_SECRET_KEY_HERE`, `YOUR_API_KEY`. Consistent with mocking & testing — this is inferred from where the key appears and what it carries, not from any published definition.

Mocking & testing x-speakeasy- namespace 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.
3 occurrences
3 documents
3 providers
vendor-named

Where it appears

Location in the documentOccurrences
securityScheme 3

What its value looks like

Value shapeOccurrences
string3

Observed values

Sampled from the specifications, most frequent first.

DUB_API_KEYYOUR_SECRET_KEY_HEREYOUR_API_KEY

Providers publishing it

All 3.

dubnovuunstructured

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 mocking & testing job.