Provenance

x-apievangelist-derived-from

`x-apievangelist-derived-from` appears in the info block. Its value is a string. Used by 7 providers across 8 OpenAPI documents. Observed values include `https://aerinmedical.com/wp-json/ (live route index + per-route`, `https://afero-docs.readthedocs.io/en/latest/CloudAPIs/`, `https://alzheon.com/wp-json/ (live route index, fetched 2026-07-31)`, `https://pay1st-docs.carry1st.com/`. 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.
8 occurrences
8 documents
7 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 8

What its value looks like

Value shapeOccurrences
string7
array1

Observed values

Sampled from the specifications, most frequent first.

https://aerinmedical.com/wp-json/ (live route index + per-routehttps://afero-docs.readthedocs.io/en/latest/CloudAPIs/https://alzheon.com/wp-json/ (live route index, fetched 2026-07-31)https://pay1st-docs.carry1st.com/https://api-syndication.dailyhunt.in/https://developer.dailyhunt.in/ads/docs/shopping-catalog/https://app2.logiless.com/developer/documents/specifications

Providers publishing it

All 7.

aerin-medicalaferoalzheoncarry1stcelsius-networkdailyhuntlogiless

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.