x-generated-note

`x-generated-note` appears at the root of the document. Its value is a string. Used by 4 providers across 10 OpenAPI documents. Observed values include `Derived operation-by-operation from the eight Postman collections AstrologyAPI p`, `Provider-published apidoc JSON (api_data.json + api_project.json, generator time`, `Derived from the Face Reading Postman collection AstrologyAPI publishes at https`, `The anonymous APIM export at https://api.equinor.com/developer/apis/iiot-ae-api-`. Consistent with documentation & dx — this is inferred from where the key appears and what it carries, not from any published definition.

Documentation & DX 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.
10 occurrences
10 documents
4 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 1
root 9

What its value looks like

Value shapeOccurrences
string9
object1

Observed values

Sampled from the specifications, most frequent first.

Derived operation-by-operation from the eight Postman collections AstrologyAPI pProvider-published apidoc JSON (api_data.json + api_project.json, generator timeDerived from the Face Reading Postman collection AstrologyAPI publishes at httpsThe anonymous APIM export at https://api.equinor.com/developer/apis/iiot-ae-api-The anonymous APIM export at https://api.equinor.com/developer/apis/recap-blueboThe anonymous APIM export at https://api.equinor.com/developer/apis/ims-export-sThe anonymous APIM export at https://api.equinor.com/developer/apis/ims-metadataThe anonymous APIM export at https://api.equinor.com/developer/apis/Timeseries-a

Providers publishing it

All 4.

airmeeastrology-apiequinorford

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 documentation & dx job.