Data & schema semantics

x-run-in-apifox

`x-run-in-apifox` appears on operations. Its value is a string. Used by 3 providers across 4 OpenAPI documents. Observed values include `https://app.apifox.com/web/project/7948067/apis/api-430293359-run`, `https://app.apifox.com/web/project/7948067/apis/api-429919472-run`, `https://app.apifox.com/web/project/7948067/apis/api-430292321-run`, `https://app.apifox.com/web/project/7948067/apis/api-428990613-run`. 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.
396 occurrences
4 documents
3 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 396

What its value looks like

Value shapeOccurrences
string396

Observed values

Sampled from the specifications, most frequent first.

https://app.apifox.com/web/project/7948067/apis/api-430293359-runhttps://app.apifox.com/web/project/7948067/apis/api-429919472-runhttps://app.apifox.com/web/project/7948067/apis/api-430292321-runhttps://app.apifox.com/web/project/7948067/apis/api-428990613-runhttps://app.apifox.com/web/project/7948067/apis/api-428749512-runhttps://app.apifox.com/web/project/7948067/apis/api-429583708-runhttps://app.apifox.com/web/project/7948067/apis/api-429003024-runhttps://app.apifox.com/web/project/7948067/apis/api-432035260-run

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.