x-tagGroups
`x-tagGroups` appears at the root of the document. Its value is a list. Used by 199 providers across 435 OpenAPI documents. Consistent with documentation & dx — this is inferred from where the key appears and what it carries, not from any published definition.
Documentation & DX
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.
435 occurrences
435 documents
199 providers
purpose-named
Where it appears
| Location in the document | Occurrences | |
|---|---|---|
| root | 435 |
What its value looks like
| Value shape | Occurrences |
|---|---|
| array | 434 |
| empty | 1 |
Providers publishing it
Showing 50 of 199.
1fort1nceaccrue-savingsaclidactivefenceadobe-suiteaffiseagorapulseairbus-oneatlasairmdralgoliaanchorageangelcamankorstorearcadiapower2asappasapp3atlaraweberbackpackbamboobevzbharti-airtelbigmlbiltbluecorebonitasoftbooking-comboxcbriabtcmarketsbud-cobullishbungalowcalifornia-privacy-protection-agencycanoe-intelligenceccpachatwootclariclear-streetclerk-comclosedloopcloudbeescloudkitchenscogniteconfluentconfluent-the-data-streaming-platformcontaboconvelioconvert
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.