Provenance

x-provenance

`x-provenance` appears in the info block. Its value is a structured object. Used by 106 providers across 519 OpenAPI documents. 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.

This one is ours. API Evangelist wrote this key into its own copies of provider specifications. It is shown for completeness — the catalog is not exempt from its own inventory.

519 occurrences

519 documents

106 providers

purpose-named

Where it appears

Location in the document	Occurrences
info	484
root	35

What its value looks like

Value shape	Occurrences
object	517
string	2

Observed values

Sampled from the specifications, most frequent first.

Shared Data Standards Body (DSB) Consumer Data Standards "CDR Bankinggenerated from the published Wealth-X API Samples Postman collection

Providers publishing it

Showing 50 of 106.

99designs adaption-labs ajaib allotex anu australian-military-bank avalara banzai bitfinder bitoasis blink-ledger-systems blockchalk brightback caamtech calm caltech carnegie-mellon-university cisco-catalyst-center cisco-ise cisco-secure-firewall cisco-umbrella codametrix columbia credgenics cybrary delphi department-of-better-technology devialet dottxt empirical-security epfl flexai fyndiq gather gemnote genlogs haekka headout highrise hku instapage kataai ketryx ku-leuven kyoto leanplum leo-labs liberate-innovations lm-studio lse

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.