Data & schema semantics

x-200

`x-200` appears on response objects. Its value is a string. Used by 3 providers across 3 OpenAPI documents. Observed values include `请求成功:`, `Create - Cash Transaction:`, `Create - Account credit Transaction:`, `Create - Wallet Transaction:`. 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.
56 occurrences
3 documents
3 providers
purpose-named

Where it appears

Location in the documentOccurrences
response 56

What its value looks like

Value shapeOccurrences
string56

Observed values

Sampled from the specifications, most frequent first.

请求成功:Create - Cash Transaction:Create - Account credit Transaction:Create - Wallet Transaction:成功:查询报价单状态成功:查询报价单币种成功:

Providers publishing it

All 3.

balad-corpchaitinxiaoman

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.