Skip to main content
Create a knowledge base when you want Fetch Hive to store content that can be searched by workflows and agents.

​
Overview

The Knowledge Bases page lists your active knowledge bases. Each row shows the knowledge base name, search type, and item count. Open a knowledge base to view analytics, add items, test search behavior, and edit the content that Fetch Hive stores as searchable chunks. Knowledge bases can also be used from workflow steps and agent tools. Use Write to Knowledge Base to add content from a workflow, Search Knowledge Base to retrieve chunks in a workflow, or Vector Search to let an agent search a knowledge base.

​
How do I create a knowledge base?

  1. Open Knowledge Bases from the sidebar.
  2. Click Add Knowledge Base.
  1. Enter a Name.
  2. Add an optional Description.
  3. Choose a Search Type:
    • Hybrid combines semantic and keyword matching.
    • Vector uses semantic similarity.
    • Full Text uses keyword search.
  4. Set Search Chunk Limit to control how many matching chunks search returns by default.
  5. Set Score Threshold to filter out lower-confidence matches.
  6. Click Save.
Fetch Hive opens the knowledge base detail page after it creates the knowledge base.

​
How do I edit knowledge base settings?

Open a knowledge base from the Knowledge Bases list. Use the breadcrumb menu next to the knowledge base name and choose the edit action. Update Name, Description, Search Type, Search Chunk Limit, or Score Threshold. Click Save Changes. These settings become the default search behavior for the knowledge base. You can still override search settings when you run a test search or configure a workflow search step.

​
How do I add an item?

Open a knowledge base and click Add Item. Enter a Name and optional Description. Choose an Item Type:
  • Custom Text - Paste or type text content directly.
  • Document Upload - Upload a file such as a PDF, Word document, text file, markdown file, CSV, or spreadsheet.
  • Website Scrape - Scrape content from a URL.
Click Save. Fetch Hive opens the item editor after it creates the item. For document items, uploaded files are stored as account assets. See Media library for how to browse shared files in your account.

​
How do I edit and process an item?

Open an item from the knowledge base item table. Update the item fields you need:
  • Name and Description for item metadata.
  • Content for Custom Text items.
  • Website URL and Response Type for Website Scrape items.
  • Document for Document Upload items.
  • Chunking Strategy for how Fetch Hive splits content before embedding.
  • Remove Email Addresses and Remove Phone Numbers when content may include personal data.
Click Save to store your changes. Click Process to generate searchable chunks. The item editor shows the current status, generated chunks, total tokens, and cost. While an item is processing, Fetch Hive disables editing actions that would conflict with the run. If processing fails, the editor shows the error message.

​
How do I control chunking?

Use Chunking Strategy in the item editor. Leave it set to Default for most items. Fetch Hive uses deterministic chunking that preserves paragraph and sentence boundaries where possible, favors speed, and avoids duplicate chunks. Choose Advanced when you need manual control. Set Maximum Chunk Length and Chunk Overlap before you process the item. Advanced uses the same boundary-aware chunking as Default, then applies overlap to preserve context between adjacent chunks. Larger chunks can preserve more context. Smaller chunks can make search results more focused. Use Testing a Knowledge Base when you want to check how the chunks behave in search.

​
How do I delete content?

To delete an item, open it in the item editor and click the delete action. Confirm the deletion in the dialog. To archive a knowledge base, open the breadcrumb menu on the knowledge base detail page and choose the archive action. Confirm the archive in the dialog. Deleting an item removes its associated vector embeddings. Archiving a knowledge base removes it from the active Knowledge Bases list. See also: Testing a Knowledge Base and Logs