Data & schema semantics

x-microcks-operation

`x-microcks-operation` appears on operations. Its value is a structured object. Used by 400 providers across 1,507 OpenAPI documents. It sits in the `x-microcks-` namespace, so its meaning is defined by microcks tooling rather than by OpenAPI. 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-microcks- 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.
21938 occurrences
1507 documents
400 providers
vendor-named

Where it appears

Location in the documentOccurrences
operation 21670
path 268

What its value looks like

Value shapeOccurrences
object21911
string27

Observed values

Sampled from the specifications, most frequent first.

{ delay: 0, dispatcher: FALLBACK }

Providers publishing it

Showing 50 of 400.

0x1password3mab-tastyabsentifyaccuweatheractive-directoryadobeadobe-analyticsadobe-campaignadobe-captivateadobe-creative-cloudadobe-creative-suiteadobe-experience-cloudadobe-illustratoradobe-launchadobe-photoshopadobe-premiereadpadvance-auto-partsadvanced-exceladvanced-micro-devicesadyenaerodataboxaffirmagcoagechecker-netagency-for-toxic-substances-and-disease-registryagent-diffagrioahasendaimlapiairbyteairflowairtablealteryxamadeusamazon-application-migration-serviceamazon-appsyncamazon-athenaamazon-audit-manageramazon-augmented-aiamazon-auroraamazon-aurora-dsqlamazon-certificate-manageramazon-codeartifactamazon-codebuildamazon-codecatalystamazon-codedeployamazon-codeguru-profiler

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.