x-logo
`x-logo` appears in the info block. Its value is a structured object. Used by 385 providers across 680 OpenAPI documents. Consistent with documentation & dx — 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 | 680 | |
| root | 3 |
What its value looks like
| Value shape | Occurrences |
|---|---|
| object | 679 |
| array | 1 |
| string | 3 |
Observed values
Sampled from the specifications, most frequent first.
Providers publishing it
Showing 50 of 385.
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.