Data & schema semantics

x-source

`x-source` appears on schema objects and properties. Its value is a structured object. Used by 127 providers across 276 OpenAPI documents. 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 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.
1044 occurrences
276 documents
127 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 193
operation 217
path 1
schema 555
securityScheme 4
root 73
header 1

What its value looks like

Value shapeOccurrences
string429
object606
array9

Observed values

Sampled from the specifications, most frequent first.

https://api.equinor.com/developer/apis/ims-export-subscriptions-v1-2/operations/https://tidal-music.github.io/tidal-api-reference/tidal-api-oas.jsonhttps://developer.sovrn.com/llms.txt (per-endpoint OpenAPI definitions, harvestehttps://github.com/yugabyte/platform-go-client/blob/master/api/openapi.yamlcollections/finalcad.postman_collection.jsonhttps://api.losant.com/https://raw.githubusercontent.com/cultuurnet/apidocs/main/../../../private/tmp/phttps://developers.kurly.com/docs/api

Providers publishing it

Showing 50 of 127.

1kosmosacmaaihubmixairport-gapakkioalsoarpeggi-labsasknicelyavis-budgetavnetbarclaysbigchaindbbolt-eubotanalyticsceroschambercj-affiliateclawvisorclevercarehealthplancodesandboxcolissimocopthiscvent-event-clouddartmouthdatadog-apmdeliverartdokki-onedynamicfeed-aieatonecoflowequinorexecution-marketfeatherlessfinalcadfinditpartsfullviewgeorgia-institute-of-technologygmi-cloudgoogle-admobgoogle-adsgospotcheckhanyanghitbtchumboldt-universitat-zu-berlinibottaiiscincogniainsiderjodokita

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.