The way you organize your indexes has a direct impact on how well agents answer questions. These best practices help you get the most out of Circuit’s search capabilities.Documentation Index
Fetch the complete documentation index at: https://docs.circuit.ai/llms.txt
Use this file to discover all available pages before exploring further.
Build larger, cohesive indexes
Circuit performs well with large indexes. Prefer consolidating related content into fewer, larger indexes rather than splitting it across many small ones. Larger indexes give agents richer context and reduce administrative overhead. Good examples:- “Technical Documentation”: all manuals, datasheets, and procedures across your product lines
- “Sales Enablement”: playbooks, battle cards, pricing guides, and case studies
- Creating a separate index for every product, team, or document type. This fragments knowledge and makes agent configuration harder.
- Splitting a single topic across many small indexes, which adds overhead without improving results.
- Having more indexes than you can reasonably maintain and keep current.
Use indexes to enforce access boundaries
The primary reason to create separate indexes is access control. Each index can be shared with different users, groups, and agents. Use this to enforce security boundaries: for example, keeping confidential HR documents separate from general product documentation.Name indexes clearly
Use names that make it obvious what’s inside, both for your team and for the agents that search them:| Instead of… | Use… |
|---|---|
| ”Docs" | "Technical Documentation" |
| "Team Stuff" | "Sales Team Playbook" |
| "Archive" | "Legacy Product Documentation (Pre-2023)” |
Maintain document freshness
Outdated documents are a common source of inaccurate answers. Build a review process:Schedule regular reviews
Check each index quarterly (or more often for fast-changing content) to identify outdated documents.
Replace outdated documents
Upload new versions rather than keeping old and new side-by-side. Two versions of the same manual can confuse the agent.
Use integrations for automated updates
If your source content lives in external systems, set up integrations to keep indexes synced automatically. This eliminates manual upload cycles and ensures agents always have the latest content.Match indexes to agent scopes
When designing your index structure, think about which agents will use them:- A field support agent might need “Product Manuals” + “Troubleshooting Guides” + “Parts Catalog”
- A sales agent might need “Product Catalogs” + “Pricing” + “Competitive Analysis”
- An RFP agent might need access to nearly everything