What it proves
Buyers can see what this pillar changes in the client app, which work it supports, and how evidence stays attached to the outcome.
Widgets
Embeddable Core-powered assistants with install snippets, origin controls, uploads, and visitor context.
Approved sources Files, apps, sites Core policy Scope and model lane Grounded answer Cited response path Visible activity Trace and usage proof
How teams inspect it
Each workflow points to visible product surfaces: active scope, source health, answer activity, cited passages, configuration controls, and usage impact.
Where it connects
This pillar links into feature pages, demos, proof sections, and pricing comparisons so teams can move from platform claim to concrete behavior.
Widgets features.
These pages give buyers a path from platform claim to concrete client-side behavior.
Public embeddable chat widgets
Publish a Core-powered assistant onto external websites.
Open feature page Widget demo and install snippetTeams can test and install embedded assistants with a generated snippet.
Open feature page Widget origin restrictionsLimit which websites are allowed to load an embedded assistant.
Open feature page Widget uploads and screen captureWebsite visitors can send files or page context into an embedded chat.
Open feature page Widget visitor formCollect visitor identity or contact context before embedded chat.
Open feature page Widget upload policiesRestrict file categories and extensions for public widgets.
Open feature page