Provenance

x-api-evangelist-provenance

`x-api-evangelist-provenance` appears in the info block. Its value is a structured object. Used by 21 providers across 61 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.
61 occurrences
61 documents
21 providers
purpose-named

Where it appears

Location in the documentOccurrences
root 15
info 46

What its value looks like

Value shapeOccurrences
object36
string25

Observed values

Sampled from the specifications, most frequent first.

Derived by the API Evangelist enrichment pipeline from the live WordPressDerived by the API Evangelist enrichment pipeline from the live WordPress REST rHarvested verbatim from cPanel''s developer portal on 2026-09-05 via the MCP tooDerived by the API Evangelist enrichment pipeline on 2026-08-23 from the live Wo

Providers publishing it

All 21.

accelaallay-therapeuticsalloplex-biotherapeuticsbelharra-therapeuticsbioaegis-therapeuticscentrexion-therapeuticscpanelflare-therapeuticsgrin-therapeuticshometrackjnana-therapeuticskriya-therapeuticsksq-therapeuticsmatchpoint-therapeuticsmbrace-therapeuticsnacuity-pharmaceuticalsneomorphnura-biostar-therapeuticstrustlyyoast

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.