We Opened Our Website Chatbot as a Public API (Here’s What You Can Build)

#javascript #webdev #ai #api

The short version

CrafterQ started as a no-code AI chatbot you drop on a website. Last week we shipped a Public API so you can keep that intelligence and throw away our UI.

Docs: crafterq.ai/docs/developers.html
Base URL: https://api.crafterq.ai/v1

Why we did this

Most website AI products force you into their bubble or corner widget. That works for a lot of marketing sites. It falls apart when you want:

A product advisor embedded in PDP / cart flows
An assistant inside a SaaS app, not only on the marketing site
A specialized Q&A experience in a customer or partner portal
A white-label agent an agency deploys for clients

In those cases the model, retrieval, conversation state, and actions still matter — the chrome doesn’t. So our chatbot became one client of the platform.

You don’t have to use the CrafterQ chatbot. You can use the CrafterQ intelligence.

What the API covers

Start and continue conversations
Stream AI responses
Retrieve conversation history
Generate follow-up questions
Collect feedback
Submit Actions (lead capture and similar) from your own forms/UI
Pull agent chat configuration

Auth: JWT bearer from agent chat_config, and/or X-CrafterQ-Chat-User for anonymous sessions. Schemas are in the OpenAPI/Redoc reference on the developers page.

Three ways to use CrafterQ now

No-code widget — fastest for marketing sites
Custom experience — your UI, our conversational backend
Embedded infrastructure — agencies / vendors building branded agents on top

Mental model

Your UI  →  CrafterQ Public API (/v1)  →  Agent trained on your content
                ↑
         JWT / X-CrafterQ-Chat-User

What I’d try first

Replace a FAQ search box with a conversational panel that still looks like your product
Add “ask about this product” on a PDP without a global chat bubble
Ship an in-app help assistant that triggers your own lead/demo Action

DEV Community