Ingestion
Parse files with verified OCR or document extraction, preserve section metadata and record document versions.
AGENT USE CASE · SOURCE-FIRST
A document agent normally combines extraction, indexed retrieval, a generation model and permissions. Embedding models support retrieval; they do not replace the agent's reasoning model.
Parse files with verified OCR or document extraction, preserve section metadata and record document versions.
Evaluate multilingual search, recall, reranking and citation alignment against representative private documents.
Filter retrieval by document-level access before sending snippets to the model; never rely on prompt instructions for access control.
Audit embeddings, logs, backups, telemetry and external connectors: a local LLM by itself does not make the whole document pipeline private.
These model records are included by catalog modality or category, not by a verified task-success benchmark. Follow their primary sources before testing.
Every step needs its own provenance, permissions and monitoring. An embedding checkpoint is not an answer-generation model.
COMMON QUESTIONS
No. It provides retrieval vectors or similarity signals. A separate controller and often a generation model are still needed.
No. Compliance depends on processing purposes, data flows, retention, permissions and legal obligations.
READ THE ORIGINALS
Neither an eligible model category nor an untested runtime implies demonstrated agent task success. For documented source claims, consult the capability evidence ledger and then apply deployment constraints in the selector.
Model metadata is source-linked; agent task success, tool-call reliability and production readiness require separate tests.
Review the methodology → Return to the explorer →