Multimodal ingestion that does not dictate your stack
OmniIngest is a multimodal ingestion framework for building reusable knowledge pipelines. It turns documents, web pages, images, and audio into validated knowledge items without the faff of stitching together one-off preprocessing scripts.
Documentation: omniingest.onrender.com
Why use OmniIngest
- Multimodal processing. PDF, DOCX, HTML, images, audio, and plain text use one pipeline model.
- Multiple model providers. Every model-backed step can select its own Pydantic AI model. Chat and embedding models are configured independently.
- Storage-independent pipelines. YAML describes transformation. CLI or Python caller chooses JSON, vector store, graph store, or another output.
- Structured when needed. JSON Schema output, jq transforms, and step validation turn model results into predictable data.
- Built for sizeable jobs. fsspec resources, concurrent stages, progress events, and stage checkpoints keep long ingestion runs manageable.
Quick start
Install command-line tool with uv:
uv tool install omni-ingest
Create a pipeline which extracts text and makes sentence-aware chunks:
pipeline_id: school_notes
domain_profile: education
steps:
- agent: text
- agent: chunking
config:
chunk_size: 900
overlap: 120
Run it against a PDF:
omni-ingest school_notes.yaml \
--input lessons/soil-erosion.pdf \
--output build/soil-erosion.json
YAML stops at transformation. Pick storage at run time:
omni-ingest school_notes.yaml --input lessons/soil-erosion.pdf --output - | jq '.items | length'
omni-ingest retrieval.yaml --input handbooks/*.pdf --output vector:default
Learn more
- Command-line usage covers files, remote resources, stdin, outputs, and resume.
- Pipeline playbook builds from simple YAML to structured output, validation, components, and model tools.
- Working with event stream covers progress and live application integration.
- API reference documents Python interfaces.
Development
git clone https://github.com/A4i-tech/OmniIngest.git
cd OmniIngest
uv sync --dev
uv run pytest tests/unit
Metadata
Release files for omni-ingest 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| omni_ingest-1.0.0.tar.gz | 52.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| omni_ingest-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 119.8 kB
Release files / omni_ingest-1.0.0.tar.gz
| Download URL | omni_ingest-1.0.0.tar.gz |
|---|---|
| Size | 52.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f09f06fa93680e061ac70112a72e8780ddc108820a1018f520395aa2e7e66da6
|
|
BLAKE2b-256 checksum How to use checksums |
1e9c3301bcadf9d98fc414adde579e338fba9b179b1e7120e0fce6b506594046
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 17, 2026.
Transparency logRelease files / omni_ingest-1.0.0-py3-none-any.whl
| Download URL | omni_ingest-1.0.0-py3-none-any.whl |
|---|---|
| Size | 67.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
728e8dfccf606f32c8739a4aba123779b593505b0806c79787d8d62c5e55ba41
|
|
BLAKE2b-256 checksum How to use checksums |
91e492ddf19bfd8600f3cb7d478f8584f5078c07c9d7e8f325ae55a7cb7abbfb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 17, 2026.
Transparency log