Data & schema semantics

x-apievangelist-source

`x-apievangelist-source` appears in the info block. Its value is a string. Used by 48 providers across 69 OpenAPI documents. Observed values include `https://perfectday.com/wp-json/wp/v2`, `https://dev.alterestate.com/ (AlterEstate Developers Center, per-operation .md d`, `https://docs.appcharge.com/api-reference (Mintlify embedded OpenAPI fragments)`, `https://help.appsamurai.com/en/articles/11105087-appsamurai-campaign-spend-api`. Consistent with data & schema semantics — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics 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.

69 occurrences

69 documents

48 providers

purpose-named

Where it appears

Location in the document	Occurrences
root	5
info	64

What its value looks like

Value shape	Occurrences
string	67
object	2

Observed values

Sampled from the specifications, most frequent first.

https://perfectday.com/wp-json/wp/v2https://dev.alterestate.com/ (AlterEstate Developers Center, per-operation .md dhttps://docs.appcharge.com/api-reference (Mintlify embedded OpenAPI fragments)https://help.appsamurai.com/en/articles/11105087-appsamurai-campaign-spend-apihttps://docs.apurata.com/POS/rest_api/https://developer.arkoselabs.com/docs/edge-api-request-parametershttps://developer.arkoselabs.com/docs/calling-verify-v4-apireconstructed from docs.bitpowr.com ReadMe per-operation OpenAPI fragments (2026

Providers publishing it

All 48.

alterestate appcharge appsamurai apurata arkose-labs bitpowr-technologies-inc bitwise blocktorch buxfer corridor cyware derivadex distru dodo ezoic flipturn funding-circle gradient hakuna harbinger-health hibachi hubilo idrx jinba kaedim kairos-ar keyo keyper komerce mashvisor moveworks-servicenow netography nift opera perfect-day permutive quantemplate rasayel recurrency ressl-ai rhizome-ai romit sentrial tank-utility weavix whoapi zenhr-inc zkme

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 data & schema semantics job.