@libra/sdk renders the full Libra chat inside an isolated iframe on your page: research over your product’s Wolters Kluwer sources, citations, the document the user is reading, assistants and workflows. No CSS conflicts, no external requests at load, no auth configuration on the host side. Current release: v ().
Quickstart
Install,
init(), attach(). A working widget in five minutes.Integration guides
Embedding, panel placement, authentication, proxy mode, locales, citations.
Capabilities
What your users get. Written for product managers and marketing.
API reference
Every
Libra.* method and every init() option.Playground
Try the widget live against staging before you write code.
Changelog
Every release, breaking changes tagged.
Who this site is for
- Engineers integrating the SDK. Every guide leads with the snippet, copied verbatim from the SDK’s README, then explains the behaviour around it.
- Product managers and marketing. The Capabilities section describes what end users see, with screenshots from the playground, and Products and sources lists which Wolters Kluwer products the SDK serves.
This site is for Wolters Kluwer product teams. The SDK is published to WK Artifactory and the WK CDN, not to the public npm registry.
A note on names
@libra/sdk is the package you install. The embedded widget is what your users see. Wolters Kluwer product and design material calls that surface the Libra Add-in — the same thing.
These docs avoid “add-in”, because in Libra’s own codebase that word means the Word and Outlook add-ins, a genuinely separate surface whose conversations are kept in their own list and never appear in the widget’s history.