Data & schema semantics

x-source

`x-source` appears in the info block. Its value is a string. Used by 100 providers across 148 OpenAPI documents. Observed values include `https://tidal-music.github.io/tidal-api-reference/tidal-api-oas.json`, `https://developer.sovrn.com/llms.txt (per-endpoint OpenAPI definitions, harveste`, `https://github.com/yugabyte/platform-go-client/blob/master/api/openapi.yaml`, `https://api.losant.com/`. 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.

161 occurrences

148 documents

100 providers

purpose-named

Where it appears

Location in the document	Occurrences
info	135
root	12
operation	13
header	1

What its value looks like

Value shape	Occurrences
string	144
object	13
array	4

Observed values

Sampled from the specifications, most frequent first.

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.yamlhttps://api.losant.com/https://developers.kurly.com/docs/apihttps://demo.asknice.ly/help/apidocs/inappReconstructed verbatim from the OpenAPI operation objects Ceros publishes in itspostman/1kosmos-postman-collection.json

Providers publishing it

Showing 50 of 100.

1kosmos adopets airport-gap akkio akool also arpeggi-labs asknicely bigchaindb blockstream bluejay-therapeutics bolt-eu botanalytics brooklinen ceros chamber cj-affiliate clawvisor clevercarehealthplan codesandbox copthis cvent-event-cloud deliverart eaton ecoflow eruditus-executive-education freight-waves fullview gospotcheck hivemapper incognia julep-beauty kita konfetti korbit kredivo kurly lanzatech larridin ledge leena-ai leeo-insurance-services linkedin liquidonate looking-glass loopme losant matrixport microsoft-azure-api-management mirrortab

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.