Data & schema semantics

x-apifox-folder

`x-apifox-folder` appears on operations. Its value is a string. Used by 3 providers across 4 OpenAPI documents. It sits in the `x-apifox-` namespace, so its meaning is defined by apifox tooling rather than by OpenAPI. Observed values include `客户`, `产品`, `7 Event Dataset/7.1 Monitored Fleet Management`, `3 History Dataset`. 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.
400 occurrences
4 documents
3 providers
vendor-named

Where it appears

Location in the documentOccurrences
operation 396
schema 4

What its value looks like

Value shapeOccurrences
string400

Observed values

Sampled from the specifications, most frequent first.

客户产品7 Event Dataset/7.1 Monitored Fleet Management3 History Dataset资产/IP地址消息推送资产/子域名任务/周期任务v2

Providers publishing it

All 3.

chaitinshipfinder-ais-data-apixiaoman

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.