Provenance

x-source-url

`x-source-url` appears in the info block and on schema objects and properties. Its value is a string. Used by 42 providers across 83 OpenAPI documents. Observed values include `https://developers.deliverect.com/reference`, `https://api.mews.com/Swagger/connector/swagger.json`, `https://docs.bluecart.com/endpoints`, `https://github.com/timbiles/Breaking-Bad--API`. Consistent with provenance — this is inferred from where the key appears and what it carries, not from any published definition.

Provenance 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.
107 occurrences
83 documents
42 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 74
root 2
schema 31

What its value looks like

Value shapeOccurrences
string107

Observed values

Sampled from the specifications, most frequent first.

https://developers.deliverect.com/referencehttps://api.mews.com/Swagger/connector/swagger.jsonhttps://docs.bluecart.com/endpointshttps://github.com/timbiles/Breaking-Bad--APIhttps://developer.dexcom.com/docs/dexcomv3/endpoint-overviewhttps://wakatime.com/developershttps://www.mediawiki.org/wiki/API:Main_pagehttps://www.mediawiki.org/wiki/API:REST_API/Reference

Providers publishing it

All 42.

0x4chan7digitalapplovinbanzaiblockbloom-creditbluecartbreaking-badcat-facts-catfactchickfilaclovercrystal-reportsdeliverectdeliveroodexcomdog-apigamerpowergiteaitsacheckmatelavulightspeed-posmews-systemsotterpaytronixrackspace-technologyrandomuserreqresrevel-systemsrijksmuseumrokuron-swanson-quotesspaceflight-newstockus-patent-and-trademark-officewakatimewikipediawikivoyagewisk-aiworkday-recruitingyugabytedbzendit

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 provenance job.