Data & schema semantics

x-apifox-folder

`x-apifox-folder` appears on operations. Its value is a string. Used by 4 providers across 24 OpenAPI documents. It sits in the `x-apifox-` namespace, so its meaning is defined by apifox tooling rather than by OpenAPI. Observed values include `Grid API`, `Partyline API/party`, `客户`, `Producer API/Overlay`. 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 x-apifox- namespace 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.
908 occurrences
24 documents
4 providers
vendor-named

Where it appears

Location in the documentOccurrences
operation 681
schema 227

What its value looks like

Value shapeOccurrences
string908

Observed values

Sampled from the specifications, most frequent first.

Grid APIPartyline API/party客户Producer API/Overlay产品7 Event Dataset/7.1 Monitored Fleet Management3 History DatasetInput&Output Module API/encoder-profile-api

Providers publishing it

All 4.

chaitinshipfinder-ais-data-apitvu-networksxiaoman

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.