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: Next: Quickstart → — full pipeline with visualization and export.
ingest → parse → semantic_extract → kgStill Unsure?
Knowledge graph vs. vector store — which do I need?
Knowledge graph vs. vector store — which do I need?
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 ConceptsI just want to run something quickly.
I just want to run something quickly.
Start with the Quickstart. It builds a complete pipeline (ingest → parse → extract → graph → visualize → export) with no API key required.
I'm adding Semantica to an existing agent — what's the minimum?
I'm adding Semantica to an existing agent — what's the minimum?
Add Context module reference →
AgentContext. It wraps your existing agent with memory, decision tracking, and precedent search — no changes to your LLM provider or agent framework needed.I need a compliance-ready pipeline — what's the minimum stack?
I need a compliance-ready pipeline — what's the minimum stack?
- Quickstart — Full pipeline in 5 minutes.
- Module Reference — Every module with examples and common chains.
- API Reference — Complete class and method documentation.
