Data & schema semantics · Identity & relationships

x-unresolved-stoplight-ref

`x-unresolved-stoplight-ref` appears on schema objects and properties. Its value is a string. Used by a single provider across 5 OpenAPI documents. Observed values include `stoplight://resources/overrides/NPaBdSGrXxc`, `stoplight://resources/overrides/wbgPBBXK2qY`, `stoplight://resources/overrides/Cvh9dy4b2Bc`, `stoplight://resources/overrides/UEKAfGKnXtA`. Consistent with identity & relationships — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics 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.
220 occurrences
5 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
schema 199
operation 20
response 1

What its value looks like

Value shapeOccurrences
string220

Observed values

Sampled from the specifications, most frequent first.

stoplight://resources/overrides/NPaBdSGrXxcstoplight://resources/overrides/wbgPBBXK2qYstoplight://resources/overrides/Cvh9dy4b2Bcstoplight://resources/overrides/UEKAfGKnXtAstoplight://resources/overrides/e716yeYODOcstoplight://resources/overrides/TefCsIHCKhsstoplight://resources/overrides/5yNhk1Hgfigstoplight://resources/overrides/DkpDaBt77Zw

Providers publishing it

All 1.

spliceforms

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.