Practical overview
When it fits
Use it when you want to set up or adapt a website-content chatbot and are prepared to configure its local development environment and required keys.
Who it is for
- Developers building a chatbot that answers questions about website content.
- Teams exploring a documentation or support assistant based on crawled pages.
- Builders who need a multi-user chat interface with username-associated conversation logs.
Documented uses
- Crawl one or more websites, including targets on different domains.
- Use indexed website content to support chatbot answers.
- Retain conversation history as context for later responses.
- Associate a conversation log with a username.
Requirements & limits
- The documented setup is local development using npm and a .env file based on env.example.txt.
- A username is required to start a chat and is associated with access to the conversation log.
- The README says a real application should authenticate users and use unique usernames.
- The repository documents an HTTP crawl endpoint with URL and page-limit parameters.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up the chatbot locally
Prepare the Next.js project for local development.
Before you start
- Git
- Node.js and npm
- The required keys for the .env file, based on env.example.txt
Steps
Clone the repository and change into the AI-Chatbot directory.
Create a .env file based on env.example.txt and add the respective keys.
Run npm install.
Run npm run dev.
Expected outcome
The README's documented local development setup is prepared and the development server is started.
Guide limitations
- The README does not specify the required environment keys or provide a verified deployment procedure.
Request a website crawl
Use the documented HTTP endpoint to request crawling of one or more URLs.
Before you start
- The application running locally at localhost:3000
Steps
Send a request to /api/crawl with a urls parameter containing the target URL or comma-separated URLs.
Include a limit parameter, as shown in the README examples.
Expected outcome
The documented endpoint receives a crawl request for the specified site or sites.
Guide limitations
- The README provides example request URLs but does not document the endpoint response or establish that a particular crawl completed successfully.
- Pages already crawled are not crawled again, according to the README.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 18 October 2026
- Original website title
- Ashot72/AI-Chatbot · Official homepage title · retained in its source language

