SDK & code generation

x-stainless-naming

`x-stainless-naming` appears on schema objects and properties. Its value is a structured object. Used by 8 providers across 8 OpenAPI documents. It sits in the `x-stainless-` namespace, so its meaning is defined by stainless tooling rather than by OpenAPI. 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-stainless- 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.
14 occurrences
8 documents
8 providers
vendor-named

Where it appears

Location in the documentOccurrences
schema 12
response 2

What its value looks like

Value shapeOccurrences
object14

Providers publishing it

All 8.

anchorbrowsercourierfireworks-aiimagekitlangdockmux-comsambanova-systemsxquik-api

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.