Cludo offers multiple AI features that enhance search results by generating answers:Documentation Index
Fetch the complete documentation index at: https://cludo.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
- AI Chat: Users ask natural language questions and receive conversational answers with citations
- AI Summary: Summarize a set of search results into a concise overview
- AI Mode: A conversational follow-up flow that starts from an AI Summary and continues with AI Chat on the same thread
Prerequisites
- AI Search enabled on your Cludo engine
- SiteKey or API Key credentials
AI Chat
AI Chat generates conversational answers grounded in your indexed content. Users ask a question, and the AI returns an answer with citations to source pages. For streaming AI Chat, citations are included inline in the streamed text by default. SettingincludeCitations does not change the streaming response.
Basic request
Multi-turn conversations
Pass theconversationId from a previous response to continue the conversation:
conversationId to start fresh.
Answer length
Control verbosity with theanswerLength parameter:
| Value | Description |
|---|---|
"comprehensive" | Full, detailed answer (default) |
"concise" | Brief, to-the-point answer |
AI Summary
AI Summary synthesizes multiple search results into a single overview. Unlike AI Chat, you first run a search, then pass selected results to the summary endpoint.Workflow
Step 1: Run a search to get results and aqueryId:
Title and Content fields when they are available.
AI Mode
AI Mode is a conversational follow-up pattern: the first answer is grounded in your search results, and every follow-up keeps the same thread. From the user’s perspective it’s typically an “Ask AI” button that opens a chat panel on the search page. It does not have its own endpoint. AI Mode uses AI Summary for the first turn and AI Chat for every follow-up, threaded together on a single conversation id.Workflow
AI Mode uses the streaming variants of both endpoints so the answers render progressively in the chat UI. Step 1: Run a search to get aQueryId and the top results, exactly as in AI Summary, Step 1.
Step 2: Send the user’s first question to the streaming AI Summary endpoint /search/summarize/stream with up to 5 source documents from Step 1 — same request body as in AI Summary, Step 2. Read the summaryRequestId from the Cludo-Summary-Request-Id response header — you’ll use it as the conversation id for every follow-up.
Step 3: Send every follow-up to the streaming AI Chat endpoint /search/answer/stream, passing the summaryRequestId from Step 2 as conversationId. Reuse the same conversationId for every subsequent follow-up so the AI keeps context.
Continuing from an AI Summary on the search page
If you already render an AI Summary above your search results, you can let users click a button on that summary to keep asking questions — without running a secondsummarize call.
The shortcut: reuse the summaryRequestId you already received from the SERP’s AI Summary as the conversationId on the first /search/answer/stream request. Display the existing summary as the first turn of the conversation client-side, then continue with the streaming AI Chat endpoint for every follow-up.
Collecting Feedback
Track user feedback to improve AI quality. Both AI Chat and AI Summary have feedback endpoints:When to Use Which
| Use Case | Feature |
|---|---|
| User asks a direct question | AI Chat |
| Show a summary above search results | AI Summary |
| Conversational follow-up questions | AI Chat |
| Synthesize specific documents | AI Summary |
| Follow-up questions on a summarized search | AI Mode |

