x-support
`x-support` appears in the info block. Its value is a string. Used by 2 providers across 9 OpenAPI documents. Observed values include `https://stackoverflow.com/questions/tagged/autodesk-platform-services`, `https://stackoverflow.com/questions/tagged/autodesk-data-management`, `https://stackoverflow.com/questions/tagged/autodesk-model-derivative`, `https://stackoverflow.com/questions/tagged/autodesk-webhooks`. 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 | 9 |
What its value looks like
| Value shape | Occurrences |
|---|---|
| string | 9 |
Observed values
Sampled from the specifications, most frequent first.
Providers publishing it
All 2.
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.