Every module works independently: import only what you need. This page maps developer goals to starting points. The Module Reference covers every module in depth.
Quick Reference
Find your goal below. The Module column is your import path; Key class is what you instantiate first.Goal-by-Goal Starting Points
Pick your goal to see the minimum imports and a working skeleton.- Build a Knowledge Graph
- Build GraphRAG
- Add Agent Memory
- Track Provenance
- Export
- MCP: Claude / Cursor
Turn documents, web pages, or databases into a structured, queryable graph.Pipeline: See the Quickstart → for a full pipeline with visualization and export.
ingest → parse → semantic_extract → kgArchitecture Selection Guidance
Knowledge graph vs. vector store selection
Knowledge graph vs. vector store selection
Use a knowledge graph (
kg) when you need structured reasoning, multi-hop traversal, provenance, or compliance audit trails.Use a vector store (vector_store) when you need fast fuzzy similarity search over large text corpora and relationships between items don’t matter.Use both together via AgentContext (GraphRAG) to get grounded LLM responses where every claim traces back to a source node.See also: Core ConceptsFast local pipeline setup
Fast local pipeline setup
Start with the Quickstart. It builds a complete pipeline (ingest → parse → extract → graph → visualize → export) with no API key required.
Minimum configuration for existing agents
Minimum configuration for existing agents
Add Context module reference →
AgentContext to equip an existing agent with memory, decision tracking, and precedent search, with no changes to your LLM provider or agent framework required.Minimum stack for compliance-ready pipelines
Minimum stack for compliance-ready pipelines
- Quickstart: full pipeline in 5 minutes.
- Module Reference: every module with examples and common chains.
- API Reference: complete class and method documentation.
