Data & schema semantics · Validation & constraints

x-last-validated

`x-last-validated` appears in the info block. Its value is a string. Used by 134 providers across 242 OpenAPI documents. Observed values include `2026-04-18`, `2026-06-02`, `2026-05-30`, `2026-04-19`. 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.
242 occurrences
242 documents
134 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 242

What its value looks like

Value shapeOccurrences
string242

Observed values

Sampled from the specifications, most frequent first.

2026-04-182026-06-022026-05-302026-04-192026-05-292026-06-032026-05-282026-05-03

Providers publishing it

Showing 50 of 134.

0x1forge4chan7digitalacronisadobe-analyticsagrioaideramazon-appflowamazon-application-discovery-serviceamazon-connectamazon-control-toweramazon-fargateamazon-fault-injection-simulatoramazon-finspaceamazon-memorydbamazon-monitronamberfloan-api-of-ice-and-fireanilistansible-automation-platformapache-activemqapache-atlasapache-bookkeeperapache-cloudstackapplovinariba-guided-buyingariba-sourcingarlulaattazure-log-analyticsblockchainbluecartbooking-holdingsbreaking-badcat-facts-catfactcataaschickfilacircanaclovercolorfulcloudsconcurdeliverectdeliveroodexcomdiscogsdisneydog-apidynatraceedamam

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.