📖 Documentation · Getting started · Supported RAG types · API reference · PyPI
Why rag-titan?
- Many RAG types, one API. Two today (
simple,adaptive), with more on the way. Switch with one word:rag_type="adaptive". - Runs 100% locally with Ollama, so your documents never leave your machine.
- Grounded answers. The model answers only from your files and cites the chunks it used.
- Chunking your way. Eight chunkers: by words, characters or model tokens (tiktoken or your own tokenizer), recursive separators, and structure-aware chunkers that keep sentences, paragraphs, heading sections or pages whole. Try them live in the chunk playground →
- PDF, Word, Markdown and text files, with paragraphs, headings and pages kept for the chunkers.
- Measure, don't guess. Compare any chunker with any RAG type on your own questions in one command (
rag-titan evaluate): recall, MRR, nDCG, answered rate and p95 time, plus every step of a run with--trace. Evaluating RAG → - Easy to read, easy to change. Short files, plain Python, and a docstring on every class. Swap any part by inheriting one base class.
Install
pip install rag-titan
ollama pull gemma3:4b && ollama pull nomic-embed-text
For token-based chunking, add the extra: pip install "rag-titan[tokens]".
Needs Python 3.10+ and Ollama. → Full setup guide
Quick start
from rag_titan import RAGTitan
rag = RAGTitan(rag_type="simple") # or "adaptive"
rag.index(["handbook.pdf", "policy.docx"])
print(rag.ask("How many leave days do I get?"))
# You get 20 paid leave days every year [chunk_0].
print(rag.run("How many leave days do I get?")["log"]) # every step it took
rag.evaluate("questions.json") # score it on your own test questions
Or from the terminal:
rag-titan ask --files handbook.pdf --question "How many leave days do I get?"
rag-titan ask --files handbook.pdf --question "How many leave days do I get?" --trace
Evaluate on your own questions
Which chunker and which RAG type work best for your documents? Write a few test questions, each naming the file (or page) that holds the answer, and compare every combination in one command:
rag-titan evaluate --files docs/*.md --questions questions.json \
--rag-type simple adaptive --chunker word paragraph
setup Recall MRR nDCG Answered Steps p50 s p95 s
simple + word 1.000 1.000 1.000 100% 3.0 0.92 1.26
adaptive + word 1.000 1.000 1.000 100% 5.0 1.67 2.02
simple + paragraph 0.917 1.000 0.936 100% 3.0 0.64 0.81
adaptive + paragraph 1.000 1.000 0.987 100% 6.3 0.96 2.91
Questions to look at:
simple + paragraph: q_006 recall 0.50 found ['remote_work.md']
Then see why one question went wrong. Here search found the right file, so the problem is the answer step, not the chunker:
$ rag-titan ask --files docs/*.md --question "Can I work from Spain for a month?" --trace
1. retrieve 7.47 ms -> 3 chunks: chunk_2 remote_work.md (0.615), chunk_0 expenses.md (0.540), ...
2. rerank 0.04 ms -> 2 chunks: chunk_2 remote_work.md (rerank 0.815), chunk_0 expenses.md (rerank 0.690)
3. generate 567.39 ms -> "I don't know based on the available documents."
Real runs with gemma3:4b on the sample policies in examples/sample_docs/. Search-only scoring
(--retrieval-only, no LLM) and the Python API are in Evaluating RAG →
Supported RAG types
rag-titan supports 2 RAG types. Pick one with rag_type. Every type has answer(), and
run() that also returns every step it took (see the steps):
| Status | RAG type | How it works | Best for | LLM calls |
|---|---|---|---|---|
| ✅ Available | Simple RAGrag_type="simple" |
Retrieve → Rerank → Generate | Fast answers to clear questions | 1 |
| ✅ Available | Adaptive RAGrag_type="adaptive" |
Route → Retrieve → Check evidence → Rewrite & retry | Mixed questions, fewer wrong answers | 2–5 |
from rag_titan import RAG_TYPES
print(RAG_TYPES) # ['simple', 'adaptive']
Coming next (not available yet): Corrective RAG · Multi-query RAG · HyDE · Hybrid RAG · Self-RAG · Parent-document RAG · Graph RAG · Agentic RAG. → Roadmap
Also included: a tool-calling agent loop. It's a separate feature, not a
rag_type.
Explore the docs
Click any picture to open its page.
|
Chunking methods |
Chunk playground |
|
Evaluating RAG |
Building blocks |
|
Extending rag-titan |
Agents |
|
Command line |
| I want to... | Read |
|---|---|
| Install it and ask my first question | Getting started |
| Pick the right RAG type | RAG types |
| Pick the right chunker | Chunking methods |
| Try the chunkers on my own text | Chunk playground |
| Compare chunkers and RAG types on my questions | Evaluating RAG |
| See why an answer went wrong | Seeing every step |
| Change models, chunk size or reranker | Configuration |
| See every class and method | API reference |
Contributing
Contributions are welcome! Read CONTRIBUTING.md to get set up. The tests run without Ollama.
License
MIT © Kumar Nishant
Metadata
Release files for rag-titan 0.6.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| rag_titan-0.6.1.tar.gz | 66.1 kB | With provenance | Details for rag_titan-0.6.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rag_titan-0.6.1-py3-none-any.whl | Python 3 | none | any | Details for rag_titan-0.6.1-py3-none-any.whl |
Total release size: 139.9 kB
Release files / rag_titan-0.6.1.tar.gz
| Download URL | rag_titan-0.6.1.tar.gz |
|---|---|
| Size | 66.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1bbc4ebc0353867c855d17f6ebcd178baf55a5a2956a2398d56e6d9726ba0dcf
|
|
BLAKE2b-256 checksum How to use checksums |
3f20b17020f1eb57ab34b4894f17816b8ca5da06d1f4989d3a0a8a78955fbc63
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.
Transparency logRelease files / rag_titan-0.6.1-py3-none-any.whl
| Download URL | rag_titan-0.6.1-py3-none-any.whl |
|---|---|
| Size | 73.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c5ae6e42080d06d8bfc7ca2bfe266ba956c27a283315e4ac60b3b91b9e1c71e5
|
|
BLAKE2b-256 checksum How to use checksums |
1d76d5547711f8098c5acbe34090383872d108729d418a685345e77fedcc4b2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.
Transparency logSecurity for rag-titan 0.6.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for rag_titan-0.6.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 10, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.