Data & schema semantics · Size & shape

x-postman-collection

`x-postman-collection` appears on operations. Its value is a string. Used by 2 providers across 4 OpenAPI documents. It sits in the `x-postman-` namespace, so its meaning is defined by postman tooling rather than by OpenAPI. Observed values include `Premium Plan (User Collection)`, `Business Plan (User Collection)`, `Face Reading Service API - Production`, `Indian Astrology PDF API collection (User Collection)`. Consistent with size & shape — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics x-postman- namespace 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.
195 occurrences
4 documents
2 providers
vendor-named

Where it appears

Location in the documentOccurrences
operation 194
info 1

What its value looks like

Value shapeOccurrences
string195

Observed values

Sampled from the specifications, most frequent first.

Premium Plan (User Collection)Business Plan (User Collection)Face Reading Service API - ProductionIndian Astrology PDF API collection (User Collection)Human Design APIs CollectionWestern Astrology PDF API (User Collection)Astrocartography Collectionhttps://raw.githubusercontent.com/inductiveautomation/83-api/main/postman/8.3.po

Providers publishing it

All 2.

astrology-apiinductive-automation

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.