Data & schema semantics · Defaults & examples

x-microcks-default

`x-microcks-default` appears on response objects. Its value is a boolean flag. Used by 442 providers across 988 OpenAPI documents. It sits in the `x-microcks-` namespace, so its meaning is defined by microcks tooling rather than by OpenAPI. Consistent with defaults & examples — 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.

30352 occurrences

988 documents

442 providers

vendor-named

Where it appears

Location in the document	Occurrences
response	26211
requestBody	4091
operation	15
components	35

What its value looks like

Value shape	Occurrences
boolean	30297
object	40
string	15

Observed values

Sampled from the specifications, most frequent first.

truefalsedefaultmultipleChoiceBatchallCategoriesgeneralKnowledgeglobalStatstokenIssued

Providers publishing it

Showing 50 of 442.

1forge 2020-police-brutality 3m 42crunch 4chan abacus abortion-policy-api absence-io abstract-api academy-software-foundation acadia acceldata accuweather acord acronis adobe adobe-analytics adobe-captivate adobe-experience-cloud adobe-launch adp adt advance-auto-parts advanced-excel advanced-micro-devices adyen aerodatabox affirm aflac agave agechecker-net agency-for-toxic-substances-and-disease-registry agent-diff agentql agify-io agilent-technologies agricultural-marketing-service agricultural-statistics-service agrio agromonitoring ahasend air-quality-programmatic-apis airbyte akri aladdin-studio alaska-air albertsons alchemy allianz-docs allianz-engagement-survey

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.