Data & schema semantics

x-source-asset

`x-source-asset` appears on operations. Its value is a string. Used by 2 providers across 7 OpenAPI documents. Observed values include `https://docs.thefork.io/assets/js/7640361e.b6bc1108.js`, `https://docs.thefork.io/assets/js/3a1abe1a.3012f03c.js`, `https://docs.thefork.io/assets/js/bf653d7c.944b4da4.js`, `https://docs.thefork.io/assets/js/caabd68a.f984be41.js`. 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.
42 occurrences
7 documents
2 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 42

What its value looks like

Value shapeOccurrences
string42

Observed values

Sampled from the specifications, most frequent first.

https://docs.thefork.io/assets/js/7640361e.b6bc1108.jshttps://docs.thefork.io/assets/js/3a1abe1a.3012f03c.jshttps://docs.thefork.io/assets/js/bf653d7c.944b4da4.jshttps://docs.thefork.io/assets/js/caabd68a.f984be41.jshttps://docs.thefork.io/assets/js/c0eb8405.19828b52.jshttps://docs.thefork.io/assets/js/41c4f519.2f982757.jshttps://docs.thefork.io/assets/js/a8fbf7bc.68c6887c.jshttps://docs.thefork.io/assets/js/9a309802.82545e3e.js

Providers publishing it

All 2.

lafourchettethefork

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.