Data & schema semantics

x-generatedAt

`x-generatedAt` appears at the root of the document. Its value is a string. Used by 4 providers across 35 OpenAPI documents. Observed values include `2021-04-19T12:58:58.637Z`, `2023-02-01T13:10:18.028Z`, `2023-02-01T12:47:28.953Z`, `2020-08-03T15:27:52.141Z`. 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.
35 occurrences
35 documents
4 providers
purpose-named

Where it appears

Location in the documentOccurrences
root 35

What its value looks like

Value shapeOccurrences
string35

Observed values

Sampled from the specifications, most frequent first.

2021-04-19T12:58:58.637Z2023-02-01T13:10:18.028Z2023-02-01T12:47:28.953Z2020-08-03T15:27:52.141Z2023-02-27T11:01:17.495Z2023-02-01T12:57:32.468Z2020-07-22T12:31:24.740Z2021-01-07T18:16:56.364Z

Providers publishing it

All 4.

amadeusamadeus-reservationsamadeus-solutionsamadeus-traveler-media

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.