Data & schema semantics · Type system

x-content-type

`x-content-type` appears on operations. Its value is a string. Used by 8 providers across 18 OpenAPI documents. Observed values include `application/json`, `application/octet-stream`, `application/x-www-form-urlencoded`, `multipart/form-data`. Consistent with type system — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics 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.
360 occurrences
18 documents
8 providers
purpose-named

Where it appears

Location in the documentOccurrences
schema 11
operation 349

What its value looks like

Value shapeOccurrences
string360

Observed values

Sampled from the specifications, most frequent first.

application/jsonapplication/octet-streamapplication/x-www-form-urlencodedmultipart/form-dataapplication/vnd.adobe.platform.sensei+json;profile=engine.v1.jsonapplication/vnd.adobe.platform.sensei+json;profile=model.v1.json

Providers publishing it

All 8.

adobe-suitebvnkkanmonsage-hrsnapvultryugabyteyugabytedb

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.