x-namespaced-enum
`x-namespaced-enum` appears on schema objects and properties. Its value is a list. Used by 27 providers across 80 OpenAPI documents. Consistent with sdk & code generation — this is inferred from where the key appears and what it carries, not from any published definition.
SDK & code generation
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.
2160 occurrences
80 documents
27 providers
purpose-named
Where it appears
| Location in the document | Occurrences | |
|---|---|---|
| schema | 2160 |
What its value looks like
| Value shape | Occurrences |
|---|---|
| array | 2160 |
Providers publishing it
All 27.
allica-bankbank-of-ireland-ukbank-of-scotlandbarclayscashpluschase-ukcouttscoventry-building-societycynergy-bankfirst-directgb-bankhampden-and-coinvesteckroolloyds-banking-groupmonument-banknatwestopen-banking-ukparagon-bankrecognise-banksantander-uksecure-trust-bankshawbrook-banktandem-bankvanquis-banking-groupyorkshire-building-societyzopa
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 sdk & code generation job.