Data & schema semantics

x-verified

`x-verified` appears on operations. Its value is a string. Used by 6 providers across 10 OpenAPI documents. Observed values include `2026-08-19`, `2026-08-06`, `2026-08-04`, `2026-08-05`. 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.
21 occurrences
10 documents
6 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 4
operation 12
parameter 1
server 2
other 2

What its value looks like

Value shapeOccurrences
string21

Observed values

Sampled from the specifications, most frequent first.

2026-08-192026-08-062026-08-042026-08-05

Providers publishing it

All 6.

adarx-pharmaceuticalskartos-therapeuticsku-leuvenrecode-therapeuticsucsfuniversity-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.