Key concepts
These are the words you'll see throughout the docs.
| Term | What it means |
|---|---|
| Project | Your product's home in the dashboard. Each project has its own agent, knowledge, conversations and public key |
| Public key | Identifies your project to the widget. Copy it from your project's Install page. It's safe to put in client code |
| Widget | The chat and voice interface the SDK adds to your site. It shows a Chat button by default |
| Robot | An animated character that can replace the Chat button. Pick classic, minimal, ink, cute, pixel or your own image. See robot types |
| AI agent | The assistant your users talk to. It reads the page, answers questions and takes actions |
| Intent | An action the agent can call, with a name, a description, parameters and a handler in your code. See Intents |
| Intent state | A named piece of app state the agent can read, such as the cart or the items on screen |
| Prompt | Instructions for the agent on the current page, set with usePrompt in React |
| Routes | The pages in your app. Share them so the agent can navigate for the user. See Routing |
| Access token | A JSON Web Token your server signs to tell VableAI who a signed-in user is. See Authentication |
| Knowledge | Articles and sources in the dashboard that the agent can draw on to answer questions |
| Conversation | A chat between a user and the agent. You can review conversations in the dashboard |
How they fit together
You create a project and copy its public key into the SDK. The SDK adds the widget to your site. When a user talks to the AI agent, it uses the page, your knowledge, intent states and prompts for context, and it can call intents or use your routes to get things done. An access token lets it know who's asking.