Data & schema semantics

x-modeled

`x-modeled` appears on operations. Its value is a boolean flag. Used by 22 providers across 28 OpenAPI documents. 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 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.
126 occurrences
28 documents
22 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 100
info 12
schema 13
requestBody 1

What its value looks like

Value shapeOccurrences
boolean122
object4

Observed values

Sampled from the specifications, most frequent first.

truefalse

Providers publishing it

All 22.

aurora-solarcastr-livecreatifydacastdat-freightgupshupnowcertspayhipprelude-soroadie-iosequence-hqsertifiersiftsigneasysinch-verifytransittrinttyntecupdoxuplistingvidu-aiyodeck-signage

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.