`x-provenance` appears in the info block and at the root of the document. Its value is a structured object. Used by 308 providers across 1,193 OpenAPI documents. Consistent with provenance — this is inferred from where the key appears and what it carries, not from any published definition.
Provenancederived 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.
Also published under another name.
This key exists in the wild spelled more than one way — differing only by case or a
hyphen, which means no tool can treat them as the same thing:
x-Provenance.
Each is catalogued separately here because that is how they exist.
1231 occurrences
1193 documents
308 providers
purpose-named
Where it appears
Location in the document
Occurrences
info
773
root
448
operation
8
securityScheme
2
What its value looks like
Value shape
Occurrences
object
1201
string
30
Observed values
Sampled from the specifications, most frequent first.
inferred-from-oidc-coreReconstructed by API Evangelist from the OpenAPI operation objects TheFork itselEndpoint paths/methods grounded in docs.mono.co (2026-07-12). Request/response sinferred-from-oidc-core rather than guessing Fudan-specific behaviour.Shared Data Standards Body (DSB) Consumer Data Standards "CDR Bankingapi-evangelist-derived-from-live-probesDerived by the API Evangelist enrichment pipeline on 2026-09-07 from the DepartmHarvested verbatim by API Evangelist for the Hydro Ottawa provider profile. This
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.