Data & schema semantics

x-assembled-from

`x-assembled-from` appears in the info block. Its value is a list. Used by 4 providers across 5 OpenAPI documents. Observed values include `506 per-endpoint OpenAPI fragments published at https://developer.synup.com/

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.
5 occurrences
5 documents
4 providers
purpose-named

Where it appears

Location in the documentOccurrences
root 1
info 4

What its value looks like

Value shapeOccurrences
array2
object2
string1

Observed values

Sampled from the specifications, most frequent first.

506 per-endpoint OpenAPI fragments published at https://developer.synup.com/

Providers publishing it

All 4.

airalogalaxy-comobserveincsynup

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.