Data & schema semantics

x-mint

`x-mint` appears on operations. Its value is a structured object. Used by 25 providers across 61 OpenAPI documents. It sits in the `x-mint-` namespace, so its meaning is defined by mint 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-mint- 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.
745 occurrences
61 documents
25 providers
vendor-named

Where it appears

Location in the documentOccurrences
operation 672
schema 61
root 12

What its value looks like

Value shapeOccurrences
object745

Providers publishing it

All 25.

anchorageatlaaugustusauthletecadanacontextdevcreditbenchmarkevermusefabric-comfinfriendliaiheygenkajabikalshilightdashloopsomnipdf-coplerionportkeyprime-intellectsendcloudsynackwriteryapily

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.