SDK & code generation

x-oracle-package

`x-oracle-package` appears at the root of the document. Its value is a string. Used by a single provider across 136 OpenAPI documents. It sits in the `x-oracle-` namespace, so its meaning is defined by oracle tooling rather than by OpenAPI. Observed values include `com.oracle.oci.usage.budgets`, `com.oracle.bmc.swagger.ocicerts`, `com.oracle.pic.email`, `com.oracle.oci.ocas.generative`. Consistent with sdk & code generation — this is inferred from where the key appears and what it carries, not from any published definition.

SDK & code generation x-oracle- 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.
136 occurrences
136 documents
1 providers
vendor-named

Where it appears

Location in the documentOccurrences
root 136

What its value looks like

Value shapeOccurrences
string136

Observed values

Sampled from the specifications, most frequent first.

com.oracle.oci.usage.budgetscom.oracle.bmc.swagger.ocicertscom.oracle.pic.emailcom.oracle.oci.ocas.generativecom.oracle.bmc.swagger.vaultcom.oracle.pic.vmware.ocvpcom.oracle.oci.waf.controlplanecom.oracle.idm.agcs.cp

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 sdk & code generation job.