x-api-evangelist-note

`x-api-evangelist-note` appears in the info block. Its value is a string. Used by 6 providers across 17 OpenAPI documents. Observed values include `Third-party profile. AeroFarms publishes no developer program; this documents th`, `Third-party profile. AEE publishes no developer program; this documents the anon`, `Published verbatim by the site itself at https://impossiblemetals.com/wp-json/tr`, `Published verbatim by the site itself at https://impossiblemetals.com/wp-json/te`. Consistent with documentation & dx — this is inferred from where the key appears and what it carries, not from any published definition.

Documentation & DX 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.
17 occurrences
17 documents
6 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 17

What its value looks like

Value shapeOccurrences
string16
object1

Observed values

Sampled from the specifications, most frequent first.

Third-party profile. AeroFarms publishes no developer program; this documents thThird-party profile. AEE publishes no developer program; this documents the anonPublished verbatim by the site itself at https://impossiblemetals.com/wp-json/trPublished verbatim by the site itself at https://impossiblemetals.com/wp-json/teHarvested verbatim from https://api.noosh.com/api/swagger.json on 2026-08-13. ThThird-party profile. Every path and parameter was read from the Unlock WordPressThird-party profile. Unlock Technologies publishes no developer program; this do

Providers publishing it

All 6.

aerofarmsaerospaceengineeringequipmentcoimpossible-metalsnooshpostexunlock

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 documentation & dx job.