Documentation & DX

x-subcategory

`x-subcategory` appears on operations. Its value is a string. Used by 17 providers across 17 OpenAPI documents. Observed values include `Private Project Articles`, `Public Article`, `Private Article`, `Private Article Files`. 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.
1271 occurrences
17 documents
17 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 1271

What its value looks like

Value shapeOccurrences
string1271

Observed values

Sampled from the specifications, most frequent first.

Private Project ArticlesPublic ArticlePrivate ArticlePrivate Article FilesPrivate CollectionPrivate Collection Private LinksPrivate ProjectPrivate Project Notes

Providers publishing it

All 17.

deakindtuerasmus-university-rotterdamfigsharehbkula-trobe-universityloughboroughmacquariestockholmuniversity-of-adelaideuniversity-of-aucklanduniversity-of-canterburyuniversity-of-rochesteruniversity-of-sheffielduniversity-of-sussexuniversity-of-the-witwatersranduon

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.