Data & schema semantics

x-run-in-apidog

`x-run-in-apidog` appears on operations. Its value is a string. Used by 5 providers across 11 OpenAPI documents. Observed values include `https://app.apidog.com/web/project/737471/apis/api-11716510-run`, `https://app.apidog.com/web/project/737471/apis/api-11716511-run`, `https://app.apidog.com/web/project/737471/apis/api-11716512-run`, `https://app.apidog.com/web/project/737471/apis/api-11716513-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.
409 occurrences
11 documents
5 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 409

What its value looks like

Value shapeOccurrences
string409

Observed values

Sampled from the specifications, most frequent first.

https://app.apidog.com/web/project/737471/apis/api-11716510-runhttps://app.apidog.com/web/project/737471/apis/api-11716511-runhttps://app.apidog.com/web/project/737471/apis/api-11716512-runhttps://app.apidog.com/web/project/737471/apis/api-11716513-runhttps://app.apidog.com/web/project/737471/apis/api-11716514-runhttps://app.apidog.com/web/project/737471/apis/api-11716515-runhttps://app.apidog.com/web/project/737471/apis/api-11716516-runhttps://app.apidog.com/web/project/737471/apis/api-11716517-run

Providers publishing it

All 5.

airalobalad-corpcardtonicenrich-sosynup

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.