Data & schema semantics

x-stoplight

`x-stoplight` appears on schema objects and properties. Its value is a structured object. Used by 22 providers across 125 OpenAPI documents. It sits in the `x-stoplight-` namespace, so its meaning is defined by stoplight tooling rather than by OpenAPI. Consistent with data & schema semantics — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics x-stoplight- 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.
6093 occurrences
125 documents
22 providers
vendor-named

Where it appears

Location in the documentOccurrences
root 82
schema 5306
response 16
requestBody 8
operation 674
tag 2
path 1
securityScheme 4

What its value looks like

Value shapeOccurrences
object6086
string7

Observed values

Sampled from the specifications, most frequent first.

null

Providers publishing it

All 22.

activefenceautodesk-bim360autodesk-fusioncreatoriqev-energyfactsetfinixfinix-paymentsironcore-labslianlian-globalmailmodonarmioctoopaquepunchhqfexqoverysaviyntsendcloudshoppabletrustlayerveho

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.