x-software
`x-software` appears in the info block. Its value is a string. Used by 9 providers across 26 OpenAPI documents. Observed values include `DSpace 5.5 (open source; the software is not a vendor tenancy)`, `Elsevier Pure (tenant khalifauniversity.elsevierpure.com)`, `Open Journal Systems 2.4.8.1 (Public Knowledge Project)`, `SimpleSAMLphp`. Consistent with data & schema semantics — 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 | 22 | |
| root | 4 |
What its value looks like
| Value shape | Occurrences |
|---|---|
| string | 22 |
| object | 4 |
Observed values
Sampled from the specifications, most frequent first.
Providers publishing it
All 9.
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.