> ## Documentation Index
> Fetch the complete documentation index at: https://sdk.docs.libratech.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Libra SDK

> Embed Libra's AI legal research chat in any Wolters Kluwer product with one script and one function call

export const sdkReleaseDate = "20 August 2026";

export const sdkVersion = "0.13.0";

`@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{sdkVersion}** ({sdkReleaseDate}).

<video autoPlay muted loop playsInline src="https://mintcdn.com/libra-sdk/urMcTJk7LWyFarvE/assets/videos/sdk-hero.webm?fit=max&auto=format&n=urMcTJk7LWyFarvE&q=85&s=27b2997696c1bcb973cce5db9dd28967" className="rounded-xl border w-full" data-path="assets/videos/sdk-hero.webm" />

<CardGroup cols={3}>
  <Card title="Quickstart" icon="rocket" href="/getting-started/quickstart">
    Install, `init()`, `attach()`. A working widget in five minutes.
  </Card>

  <Card title="Integration guides" icon="plug" href="/guides/embedding">
    Embedding, panel placement, authentication, proxy mode, locales, citations.
  </Card>

  <Card title="Capabilities" icon="sparkles" href="/capabilities/overview">
    What your users get. Written for product managers and marketing.
  </Card>

  <Card title="API reference" icon="book-open" href="/reference/api">
    Every `Libra.*` method and every `init()` option.
  </Card>

  <Card title="Playground" icon="flask-conical" href="/getting-started/playground">
    Try the widget live against staging before you write code.
  </Card>

  <Card title="Changelog" icon="history" href="/changelog">
    Every release, breaking changes tagged.
  </Card>
</CardGroup>

## 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](/capabilities/overview) section describes what end users see, with screenshots from the playground, and [Products and sources](/capabilities/products-and-sources) lists which Wolters Kluwer products the SDK serves.

<Note>
  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.
</Note>

## 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.

<Tip>
  **Before your first integration call:** every domain you embed on has to be registered with Libra in advance, including localhost and staging. It is the single most common reason a first integration appears to hang on the sign-in screen. [Authentication](/guides/authentication#register-your-domain-before-you-go-live)
</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.