Security

x-amz-server-side-encryption

`x-amz-server-side-encryption` appears on header objects. Its value is a structured object. Used by 2 providers across 2 OpenAPI documents. It sits in the `x-amz-` namespace, so its meaning is defined by amz tooling rather than by OpenAPI. Consistent with security — this is inferred from where the key appears and what it carries, not from any published definition.

Security x-amz- 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.

5 occurrences

2 documents

2 providers

vendor-named

Where it appears

Location in the document	Occurrences
header	4
response	1

What its value looks like

Value shape	Occurrences
object	4
string	1

Observed values

Sampled from the specifications, most frequent first.

AES256

Providers publishing it

All 2.

amazon-s3 narmi

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 security job.