Website chatbot
A website chatbot-style experience powered by STYD can be built as a custom project, using your own backend that calls the STYD API.
There is no drop-in STYD chat widget, iframe, official embed script, or self-service chatbot. A public chatbot is a custom architecture, not a finished product feature.
The safe shape
If you build something like this, your website talks to your own backend, and only the backend calls STYD. The API key stays on the server.
Never put a STYD API key in frontend or client-side code. Anyone could read it from the browser.
What public-facing use demands
Access control
Decide who can use it and how requests are authorised.
Decide who can use it and how requests are authorised.
Data-scope design
Carefully limit what data the chatbot is allowed to reach and answer about.
Carefully limit what data the chatbot is allowed to reach and answer about.
Rate & usage planning
Public traffic consumes workspace usage; plan for it.
Public traffic consumes workspace usage; plan for it.
Output control & moderation
Control, validate, and moderate what the chatbot is allowed to say.
Control, validate, and moderate what the chatbot is allowed to say.
A pattern, not a product
This is a custom project, not a finished feature of STYD. Public chat experiences need custom output control, moderation, scope design and validation. See the catalogue of custom builds or contact STYD from the support page to discuss whether this fits your use case.