Data & schema semantics · Identity & relationships

x-related-resource

`x-related-resource` appears on operations. Its value is a string. Used by a single provider across 158 OpenAPI documents. Observed values include `#/definitions/WorkRequest`, `#/definitions/ManagedDatabase`, `#/definitions/WorkRequestError`, `#/definitions/WorkRequestLogEntry`. Consistent with identity & relationships — 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.

5821 occurrences

158 documents

1 providers

purpose-named

Where it appears

Location in the document	Occurrences
operation	5808
path	11
response	2

What its value looks like

Value shape	Occurrences
string	5821

Observed values

Sampled from the specifications, most frequent first.

#/definitions/WorkRequest#/definitions/ManagedDatabase#/definitions/WorkRequestError#/definitions/WorkRequestLogEntry#/definitions/BdsInstance#/definitions/DatabaseInsights#/definitions/ManagedInstance#/definitions/Job

Providers publishing it

All 1.

oracle

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.