x-apievangelist-derived-from
`x-apievangelist-derived-from` appears in the info block. Its value is a string. Used by 5 providers across 6 OpenAPI documents. Observed values include `https://afero-docs.readthedocs.io/en/latest/CloudAPIs/`, `https://pay1st-docs.carry1st.com/`, `https://api-syndication.dailyhunt.in/`, `https://developer.dailyhunt.in/ads/docs/shopping-catalog/`. Consistent with provenance — this is inferred from where the key appears and what it carries, not from any published definition.
Where it appears
| Location in the document | Occurrences | |
|---|---|---|
| info | 6 |
What its value looks like
| Value shape | Occurrences |
|---|---|
| string | 5 |
| array | 1 |
Observed values
Sampled from the specifications, most frequent first.
Providers publishing it
All 5.
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.