`x-apievangelist-source` appears in the info block. Its value is a string. Used by 53 providers across 147 OpenAPI documents. Observed values include `https://perfectday.com/wp-json/wp/v2`, `https://api-library-marketplace.adp.com/hcm-offrg-wfn/benefits/beneficiaries/v1/`, `https://api-library-marketplace.adp.com/hcm-offrg-wfn/benefits/dependents/v1/dep`, `https://api-library-marketplace.adp.com/hcm-offrg-wfn/benefits/external-plans/v1`. Consistent with data & schema semantics — this is inferred from where the key appears and what it carries, not from any published definition.
Data & schema semanticsderived 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.
147 occurrences
147 documents
53 providers
purpose-named
Where it appears
Location in the document
Occurrences
info
129
root
18
What its value looks like
Value shape
Occurrences
string
131
object
16
Observed values
Sampled from the specifications, most frequent first.
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.