Provenance

x-generated-by

`x-generated-by` appears in the info block and at the root of the document. Its value is a string. Used by 50 providers across 83 OpenAPI documents. Observed values include `claude-crawl-2026-05-08`, `API Evangelist enrichment pipeline`, `api-evangelist-enrichment`, `api-evangelist enrichment pipeline`. Consistent with provenance — this is inferred from where the key appears and what it carries, not from any published definition.

Provenance 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.

83 occurrences

83 documents

50 providers

purpose-named

Where it appears

Location in the document	Occurrences
info	57
root	26

What its value looks like

Value shape	Occurrences
string	83

Observed values

Sampled from the specifications, most frequent first.

claude-crawl-2026-05-08API Evangelist enrichment pipelineapi-evangelist-enrichmentapi-evangelist enrichment pipelineapi-evangelist-enrichment-pipelineAPI Evangelist enrichment pipeline (derived from the first-party Postman collectAPI Evangelist enrichment pipeline (local-v3)API Evangelist enrichment pipeline — mechanical transform of the provider-served

Providers publishing it

All 50.

1kosmos 3vjia-technology 91squarefeet acma aegis-marine-shipmanagement also aptargroup arpeggi-labs asknicely boston-properties cerner clawvisor clevercarehealthplan cms-gov code-ocean deliverart doe dokki-one domob finalcad finditparts google-ads greif kita korbit kurly larridin leankit leaseaccelerator liquid-death liquidonate litmus-hiring looking-glass mixrank ontario-energy-board opkey oracle-health paymate re reachware-inc shopgo southern-california-edison speccheck truvideo utilita videoverse zenadmin zenledger zipline-ai zircuit

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 provenance job.