Documentation & DX

x-source-documentation

`x-source-documentation` appears on operations. Its value is a string. Used by 3 providers across 3 OpenAPI documents. Observed values include `https://dev.3vjia.com/document?apiId=646398030987284576`, `https://dev.3vjia.com/document?apiId=456509490821398562`, `https://dev.3vjia.com/document?apiId=832299125029617719`, `https://dev.3vjia.com/document?apiId=713058818141077606`. Consistent with documentation & dx — this is inferred from where the key appears and what it carries, not from any published definition.

Documentation & DX 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.
431 occurrences
3 documents
3 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 429
info 2

What its value looks like

Value shapeOccurrences
string431

Observed values

Sampled from the specifications, most frequent first.

https://dev.3vjia.com/document?apiId=646398030987284576https://dev.3vjia.com/document?apiId=456509490821398562https://dev.3vjia.com/document?apiId=832299125029617719https://dev.3vjia.com/document?apiId=713058818141077606https://dev.3vjia.com/document?apiId=713058818141077585https://dev.3vjia.com/document?apiId=791618173400137763https://dev.3vjia.com/document?apiId=769625759609405570https://dev.3vjia.com/document?apiId=769625759609405589

Providers publishing it

All 3.

3vjia-technologyleaseacceleratorliquid-death

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 documentation & dx job.