Data & schema semantics

x-verified

`x-verified` appears on operations. Its value is a structured object. Used by 10 providers across 18 OpenAPI documents. 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 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.
142 occurrences
18 documents
10 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 134
info 1
securityScheme 1
parameter 1
server 2
other 3

What its value looks like

Value shapeOccurrences
object110
string31
boolean1

Observed values

Sampled from the specifications, most frequent first.

2026-08-192026-10-08false

Providers publishing it

All 10.

aimodelconsol-energydirector-of-national-intelligencefederal-accounting-standards-advisory-boardfederal-mediation-and-conciliation-serviceku-leuvenoddsrelaypaymateucsfuniversity-of-chicago

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.