x-origin
`x-origin` appears in the info block. Its value is a list. Used by 125 providers across 166 OpenAPI documents. Observed values include `origin`. Consistent with provenance — this is inferred from where the key appears and what it carries, not from any published definition.
Where it appears
| Location in the document | Occurrences | |
|---|---|---|
| info | 166 | |
| root | 2 |
What its value looks like
| Value shape | Occurrences |
|---|---|
| array | 164 |
| object | 2 |
| string | 2 |
Observed values
Sampled from the specifications, most frequent first.
Providers publishing it
Showing 50 of 125.
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.