x-code-samples
`x-code-samples` appears on operations. Its value is a list. Used by 30 providers across 50 OpenAPI documents. 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
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.
2593 occurrences
50 documents
30 providers
purpose-named
Where it appears
| Location in the document | Occurrences | |
|---|---|---|
| operation | 2541 | |
| path | 3 | |
| schema | 48 | |
| root | 1 |
What its value looks like
| Value shape | Occurrences |
|---|---|
| array | 2544 |
| object | 49 |
Providers publishing it
All 30.
adafruit-ioahasendapperioauthleteavayaaweberbezero-carbonblubrry-api-restful-api-for-podcast-publishing-statisticsbtcmarketsch-robinson-worldwidecognitegridx-aikore-wirelesslatokenmoengagenylasovh-cloudparallelparallel-aiphraseportkeyrocketreachshutterstockskai-kenshoostytchtopitransunionwhen-i-workwso2zuora
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.