Documentation

Practicl answers questions from the sources you connect: the documents you upload, and your website. These pages cover putting it in front of your customers. A share link answers from the documents you choose; the widget answers from your website.

New here? The quickstart goes from an empty account to a customer asking your datasheet questions. It is the fastest way to see whether this is any good on your documents, and most of that time is spent waiting rather than working.

Three ways to integrate

In increasing order of effort. Most people need only the first.

Share link — no code

Mint a scoped share key in the dashboard and send a URL. The link opens the full workspace — a side-by-side PDF viewer and chat scoped to the documents you chose — with nothing to build on your side. See Share links.

Embed the widget — one script tag

Drop one script tag on your own site to add a chat bubble. It mounts inside a shadow DOM so its styles cannot collide with your page, and it themes itself from your config — accent colour, greeting, and corner position. See Embed the widget.

<script src="https://app.staging.practicl.io/widget.bundle.js"
        data-api-key="pk_live_..."
        data-source-id="SOURCE_UUID"
        data-api-base="https://api.staging.practicl.io"
        data-app-url="https://app.staging.practicl.io"
        defer></script>

REST API — full control

Call the API from your own UI or backend and render answers however you like. The chat endpoint streams answers token by token over Server-Sent Events, with sources returned when the answer completes. See API reference.

Before you build

Two pages that are worth the ten minutes if you are integrating rather than trying it out.

How Practicl is organised — products, documents, share links, scope and personas. Most of what goes wrong later is one of these assumed rather than read, and the one that costs the most is discovering how coarsely you divided your products after you have uploaded forty datasheets into one.

Security model — what a key opens, what it cannot do, and what is checked on every request. This is the page to forward when someone asks whether they can put it on the website.

How answers behave

Answers come only from your own documents. They preserve exact values, cite the page they came from, and decline when the document does not cover the question — which, for a datasheet, is the behaviour you want.