RAG Knowledge Base
<div class="post-category"><span class="cat-badge cat-setup">Setup</span></div>
<p class="lead"><strong>The RAG Knowledge Base is the shared Qdrant vector store at 10.50.0.2:6333 that backs every BizNode-powered bot with retrieval-augmented generation. Because it is centralized, updates to the KB propagate instantly to every node.</strong></p>
<h2>Overview</h2>
<p>Basic tier bots query the `biznode_fv` collection; Pro tier bots query `biznode_dx`. Embeddings are generated through the NodeMonitor LLM gateway (default model qwen3:14b on admin) and stored with stable ids. This KB seeder publishes canonical facts that bots cite in customer conversations.</p>
<h2>Key components</h2>
<ul><li>Qdrant vector store at 10.50.0.2:6333</li><li>Collections: `biznode_fv` (Basic), `biznode_dx` (Pro)</li><li>Embeddings via NodeMonitor gateway</li><li>Seeded from blog KB articles and support docs</li><li>Idempotent upserts keyed by stable id</li></ul>
<h2>Related</h2>
<ul><li>[NodeMonitor Gateway](/post.php?slug=nodemonitor-gateway)</li><li>[Blog Node](/post.php?slug=blog-node)</li><li>[BizNode Node](/post.php?slug=biznode-node)</li></ul>
Powered by BizNode™
Related Posts
Add a Command to Your Bot in 10 Lines of YAML
Adding a new bot feature used to mean editing Python, wiring a `CommandHandler`, and redeploying. With the Feature Manifest Framework it is four steps and about ten lines of YAML — and you get a slash command and a paid network handle from
How 1BZ Bots Define Features via Manifest
1BZ bots used to hand-wire every capability as a Python `CommandHandler`. That put even a trivial command one code change and a redeploy away from production. The Feature Manifest Framework replaces that with a declarative YAML file at `bot
Slash Command vs Handle — what each is for
Slash commands and handles are related but not identical. A slash command is the owner-facing UI inside a single bot; a handle is a network-facing service endpoint that any other bot, workflow, or API on the 1BZ network can call. The same u