Skip to main content
Ragrails turns source content into a retrieval-ready knowledge base. It extracts content from websites, documents, REST APIs, or Markdown, then chunks, embeds, stores, retrieves, and chats over that content through the SDK, CLI, or REST API. Use it when you need AI search, grounded chat, support agents, documentation assistants, internal knowledge bases, or API copilots backed by your own data.

What Ragrails gives you

Install

For website crawling, install URL support and set up a browser once:
See Installation for provider and vector database extras.

Quick Path

This example builds a support collection from one document, searches it, then asks a grounded chat question. The sample source says: “Customers can request a refund within 30 days of purchase.”

Source Types

Use one source type or combine several in the same ingest() call.
SDK defaults live in RagRails(...); CLI defaults live in .ragrails.toml; REST requests pass configuration in each request body.

Where To Go Next

Quickstart

Build a working knowledge base and chat flow quickly.

How RAG Works

Learn the pipeline terms before tuning them.

Pipeline Overview

See extraction, chunking, embedding, storing, retrieval, chat, and maintenance together.

Capabilities

Turn on reranking, rewriting, quality controls, streaming, resilient ingestion, and tools.

Use Cases

Pick a strong sample: support agent, docs assistant, internal KB, AI search, or API copilot.

Walkthroughs

Follow source-specific setup paths for websites, documents, APIs, or REST hosting.

Interfaces

Common Production Steps

  1. Add Reranking when search results are relevant but poorly ordered.
  2. Add Query Rewriting for follow-up questions.
  3. Add Chat Tuning before exposing answers to users.
  4. Add Streaming for long crawls or responsive chat UIs.
  5. Add Knowledge Base Maintenance so changed and deleted source content stays in sync.