Browse the docs
Getting started
How ASDK works
The parts of ASDK and how they connect: workspaces, sites, the knowledge base, agents, the widget script and the dashboard pages where you manage each one.
Last updated
On this page
ASDK puts AI agents on your website. You connect a site, ASDK reads it into a knowledge base, and the agents you switch on answer from that knowledge through one script on your pages. This page explains how the parts fit together and where you manage each one in the dashboard.
The building blocks
| Part | What it is | Where you manage it |
|---|---|---|
| Workspace | Your company's space in ASDK: its sites, team and plan | Workspace switcher, Settings → Workspace |
| Site | One website your agents work on | Sites |
| Knowledge | What the agents know about one site | Knowledge |
| Agents | The jobs ASDK does on the site, such as answering questions | Agents |
| Widget | The chat button and panel visitors use | Agents (settings), Install (snippet) |
| Inbox | Conversations, leads and what visitors ask | Inbox |
Workspaces
A workspace holds sites, knowledge, agents and a team. The plan, its limits and its members belong to the workspace, so an agency or a company with several brands can keep them apart in separate workspaces. You can belong to several workspaces and switch between them at the top of the sidebar. See Workspaces.
Sites
A site is one website, identified by its address, such as https://acme.com. Each site gets its own knowledge, widget settings and Site ID. The Site ID (site_ followed by 20 letters and digits) is what connects the script on your pages to the right site. Your plan decides how many sites a workspace can have; see Plans and limits.
Each site also has a list of Allowed domains: the widget only works on pages of those domains, so nobody can put your agent on another website. When you add a site, its address and its www variant are allowed. You can add more, such as a shop on a subdomain, in the site's settings.
How knowledge is built
When you add a site, ASDK's crawler, ASDK-Crawler, reads its public pages the way a search engine does. It follows your robots.txt rules; the crawler page explains how it identifies itself. You can add more sources to the same knowledge:
- Website sections and sitemaps, to control which pages are read.
- Files, such as PDFs and Word documents, for content that isn't on your site.
- Text snippets, for short facts written straight into ASDK.
- Q&A pairs, for questions that need one exact answer.
ASDK splits each page and document into short passages, stores them in a search index of its own for your site and keeps them up to date: websites and sitemaps are read again every day, or every week on the Free plan, and only changed pages are processed again. The knowledge base explains the technical side, including chunkingChunking is splitting long documents into smaller passages before indexing, so an AI system can retrieve just the part of a page that answers a question. and embeddingsEmbeddings are lists of numbers that represent the meaning of a piece of text, so software can find related content by measuring how close two lists are..
How an answer is made
A visitor asks
The visitor types a question in the widget, in any language.
ASDK looks up your knowledge
It searches your site's knowledge for the passages that match the question best. A Q&A pair that matches the question is preferred over passages from pages.
The agent writes the answer
A language model writes a short answer from those passages only and cites the pages it used. This approach is called retrieval-augmented generationRetrieval-augmented generation (RAG) is a technique where an AI system first looks up relevant documents, then writes its answer using what it found..
No match, no guess
If your knowledge has nothing that answers the question, the agent says it doesn't know and, depending on your lead capture setting, offers a form so you can follow up. The question is recorded as a knowledge gap you can fill later.
Every answer counts toward your plan's monthly answers; see What counts as an answer.
Agents
An agent is one job ASDK does on your site. All of them share the same knowledge, so switching one on doesn't mean setting up content again. Chat, Sales and Agent-Ready are in early access; Search, Forms and Voice are coming soon. Choosing agents helps you pick, and Agents describes each one.
The widget on your site
One script tag loads everything:
<script async src="https://cdn.asdk.com/v1/asdk.js" data-site-id="SITE_ID"></script>The script is small and loads without slowing your page. It draws the chat button, and loads the chat panel only when a visitor opens it. It runs inside its own isolated area of the page, so your site's styles don't change it and it doesn't change your site. It sets no cookies: it keeps a random visitor ID in the browser's local storage, so a conversation continues when the visitor moves to another page.
Because everything else comes from the dashboard, you install the script once. Changing colors, texts or agents later needs no change to your site: visitors see saved settings on the next page view.
The dashboard
The dashboard at app.asdk.com has these pages:
- Overview: where to start and, as it rolls out, your key numbers.
- Sites: add, rename, pause or delete sites and edit their allowed domains.
- Knowledge: sources, pages and Q&A pairs of each site.
- Inbox: conversations and leads. See Conversations.
- Agents: switch agents on and set the widget's look, texts, suggested questions and lead capture.
- Install: the snippet, platform guides and Check installation.
- Billing: your current plan.
- Settings: Workspace, Members and API keys.
Owners and admins can change everything; members can work with knowledge and view the rest. See Members and roles.
Early access
ASDK is in early access. Agents marked "early access" work today and are still improving; "coming soon" agents and features are not available yet. Billing is coming soon too: Plans and limits explains how to change plans in the meantime.