Data & schema semantics

x-amz-target

`x-amz-target` appears on operations. Its value is a string. Used by 4 providers across 4 OpenAPI documents. It sits in the `x-amz-` namespace, so its meaning is defined by amz tooling rather than by OpenAPI. Observed values include `FmrsService.CreateTask`, `FmrsService.ListTasks`, `FmrsService.DescribeTask`, `FmrsService.StartTaskExecution`. Consistent with data & schema semantics — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics 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.
33 occurrences
4 documents
4 providers
vendor-named

Where it appears

Location in the documentOccurrences
operation 33

What its value looks like

Value shapeOccurrences
string33

Observed values

Sampled from the specifications, most frequent first.

FmrsService.CreateTaskFmrsService.ListTasksFmrsService.DescribeTaskFmrsService.StartTaskExecutionFmrsService.CreateLocationS3FmrsService.CreateAgentDynamoDB_20120810.CreateTableDynamoDB_20120810.DescribeTable

Providers publishing it

All 4.

amazon-datasyncamazon-dynamodbamazon-shieldamazon-storage-gateway

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.