Data & schema semantics

x-microcks-operation

`x-microcks-operation` appears on operations. Its value is a structured object. Used by 625 providers across 1,583 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.
26468 occurrences
1583 documents
625 providers
vendor-named

Where it appears

Location in the documentOccurrences
operation 26160
path 308

What its value looks like

Value shapeOccurrences
object25959
string509

Observed values

Sampled from the specifications, most frequent first.

*id001{ delay: 0, dispatcher: FALLBACK }{delay: 0, dispatcher: FALLBACK}&id001

Providers publishing it

Showing 50 of 625.

0x1forge1password2020-police-brutality3m42crunch4chan7digitalab-tastyabacusabortion-policy-apiabsence-ioabsentifyabstract-apiacademy-software-foundationacadiaacceldataaccuweatheracordacronisactive-directoryadobeadobe-analyticsadobe-campaignadobe-captivateadobe-creative-cloudadobe-creative-suiteadobe-experience-cloudadobe-illustratoradobe-launchadobe-photoshopadobe-premiereadpadtadvance-auto-partsadvanced-exceladvanced-micro-devicesadyenaerodataboxaffirmaflacagaveagcoagechecker-netagency-for-toxic-substances-and-disease-registryagent-diffagentqlagify-ioagilent-technologiesagricultural-marketing-service

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.