Skip to main content
Agentic retrieval uses an LLM to understand complex queries, decompose them into sub-queries, and intelligently aggregate results. While it has higher latency (2-5 seconds), it excels at nuanced questions that simple keyword or vector search can’t handle well.

How Agentic Retrieval Works

The agent:
  1. Analyzes the query to understand intent
  2. Decomposes into multiple sub-queries
  3. Executes each sub-query using hybrid search
  4. Aggregates and re-ranks results by relevance

When to Use Agentic Retrieval

Good Candidates for Agentic

Better Suited for Hybrid

Basic Usage

Complex Query Examples

Example 1: Meeting Preparation

Example 2: Decision History

Example 3: Relationship Analysis

Cost and Latency Considerations

Agentic retrieval has higher resource usage:

Optimizing Agentic Queries

Fallback Strategy

Implement a tiered retrieval strategy:

Async Client with Longer Timeouts

For production use, handle agentic retrieval’s longer latency:

Best Practices

Write detailed queries that explain what context you need:
Always use appropriate timeouts and fallbacks:
Cache results for repeated complex queries:
Reserve agentic for high-value queries where accuracy matters:

Next Steps

Concepts Guide

Compare all retrieval methods

Python Integration

Production patterns with timeout handling