Skip to main content

CDN versioning

Every embed asset is served from a version-pinned path:

https://cdn.kaleidr.com/embed/v1/kaleidr.js   ← the loader (façade)
https://cdn.kaleidr.com/embed/v1/chat.js      ← chat bundle
https://cdn.kaleidr.com/embed/v1/viewer.js    ← viewer loader
https://cdn.kaleidr.com/embed/v1/editor.js    ← editor bundle
https://cdn.kaleidr.com/embed/v1/tile.js      ← tile loader

You pin kaleidr.js; it requests the v1 of each product bundle in turn.

How versions change​

  • Backward-compatible changes ship in place under /embed/v1/ — you get them automatically.
  • A breaking wire/postMessage change ships a new major beside v1: /embed/v2/kaleidr.js (+ /embed/v2/<product>.js). Your pinned v1 URL keeps working unchanged; migrate on your own schedule by bumping the path.

The SSE wire contract is versioned the same way at /inference-api/b2b/v1/* — a v2 only appears for a breaking stream change.

Caching​

Bundles are served with a short cache TTL so fixes propagate quickly; don't fingerprint or self-host copies unless you intend to pin a specific build.