Data & schema semantics · Validation & constraints

x-invalid

`x-invalid` appears on parameter objects. Its value is a string. Used by a single provider across 2 OpenAPI documents. Observed values include `foo`, `123`, `afc168-ff1d-4858-955e-4a375189ecdd`, `afc168-ff1d-4858-955e-4a375189ecd`. Consistent with validation & constraints — 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.

28 occurrences

2 documents

1 providers

purpose-named

Where it appears

Location in the document	Occurrences
parameter	25
operation	3

What its value looks like

Value shape	Occurrences
string	18
integer	10

Observed values

Sampled from the specifications, most frequent first.

foo123afc168-ff1d-4858-955e-4a375189ecddafc168-ff1d-4858-955e-4a375189ecdafc168-ff1d-4858-955e-4a375189ec-1

Providers publishing it

All 1.

cox-automotive

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.