SDK & code generation

x-speakeasy-server-id

`x-speakeasy-server-id` appears in the document and on server objects. Its value is a string. Used by 4 providers across 5 OpenAPI documents. It sits in the `x-speakeasy-` namespace, so its meaning is defined by speakeasy tooling rather than by OpenAPI. Observed values include `prod`, `sandbox`, `production`, `saas-api`. Consistent with sdk & code generation — this is inferred from where the key appears and what it carries, not from any published definition.

SDK & code generation 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.
8 occurrences
5 documents
4 providers
vendor-named

Where it appears

Location in the documentOccurrences
other 5
server 3

What its value looks like

Value shapeOccurrences
string8

Observed values

Sampled from the specifications, most frequent first.

prodsandboxproductionsaas-apidevelopmentplatform-apistaging

Providers publishing it

All 4.

gr4vyspeakeasyunstructuredwingspan

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 sdk & code generation job.