Data & schema semantics · Type system

x-spec-enum-id

`x-spec-enum-id` appears on schema objects and properties and on operations. Its value is a string. Used by 8 providers across 17 OpenAPI documents. Observed values include `65feb4244cc9110c`, `2696b7065f33307c`, `7b8d0e83a4bb5178`, `ca933c38b935e547`. 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.
2467 occurrences
17 documents
8 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 1188
schema 1279

What its value looks like

Value shapeOccurrences
string2467

Observed values

Sampled from the specifications, most frequent first.

65feb4244cc9110c2696b7065f33307c7b8d0e83a4bb5178ca933c38b935e5470a239d878b6666a40b3bfadcebd86b5880d251a40f3a31442f2fe6dcdc7772bd

Providers publishing it

All 8.

adro1b33edf-energykarrioledgernetboxorigin-energysakura-internetwisdomtree

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.