intextum-worker
The Intextum processing worker: an HTTP-polling worker that pulls tasks from an Intextum API instance and runs the Docling / FFmpeg document, image and audio pipeline (OCR, ASR, chunking, classification, content enrichment, embeddings).
The worker is always-remote: it downloads source files from and uploads results to the API over HTTP, so it does not need a shared volume and can run anywhere — including on a host with a GPU while the rest of the stack runs in Docker.
Install
Pick the bundle that matches your accelerator. The macOS (Apple MPS) wheels are on PyPI, so it installs with no extra flags:
pip install 'intextum-worker[mps]'
Linux CPU and NVIDIA CUDA pull their Torch build from the PyTorch index, so add
the matching --extra-index-url:
# Linux, CPU only
pip install 'intextum-worker[cpu]' --extra-index-url https://download.pytorch.org/whl/cpu
# Linux, NVIDIA CUDA 12.6
pip install 'intextum-worker[cuda]' --extra-index-url https://download.pytorch.org/whl/cu126
Available extras: mps, cpu, cuda, cpu-document (document/image only), plus
the granular document, asr, enrichment stacks.
Run
export API_URL="https://your-intextum-host" # the API to poll
export WORKER_TOKEN="<token from the Add Worker dialog>"
intextum-worker --capabilities document,video,image
intextum-worker --help lists all flags. Every flag also has an environment
variable (API_URL, WORKER_TOKEN, WORK_DIR, CAPABILITIES, POLL_INTERVAL,
CLASSIFICATION_DEVICE, DOCLING_OCR_ENGINE, …); CLI flags take precedence.
Development
This package uses a src/ layout. The repo-root VERSION file is the single
source of truth for the version; it is staged into worker/VERSION at build time
(worker/VERSION is gitignored).
cp ../VERSION VERSION # stage the version for an editable install
pip install -e '.[mps,test]' # or [cpu,test] / [cuda,test]
pytest
export API_URL="http://localhost:8000"
export WORKER_TOKEN="<token from the Add Worker dialog>"
export CLASSIFICATION_DEVICE="mps" # macOS Apple Silicon; use cpu/cuda elsewhere
intextum-worker --capabilities document,video,image,training
Metadata
Release files for intextum-worker 0.1.14
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| intextum_worker-0.1.14.tar.gz | 112.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| intextum_worker-0.1.14-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 207.0 kB
Release files / intextum_worker-0.1.14.tar.gz
| Download URL | intextum_worker-0.1.14.tar.gz |
|---|---|
| Size | 112.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d81c315fc93f2c74ab54077342a036a302b04cd3094204872acdd288454e2949
|
|
BLAKE2b-256 checksum How to use checksums |
45e130369f31435b6824e3b698ec110660203d4e94682cc2c4c8a9f69993fb49
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 2, 2026.
Transparency logRelease files / intextum_worker-0.1.14-py3-none-any.whl
| Download URL | intextum_worker-0.1.14-py3-none-any.whl |
|---|---|
| Size | 94.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0a6e7b4c8732f487995ffe0899c0106ab26208e0d667033f9664aca23948cc3b
|
|
BLAKE2b-256 checksum How to use checksums |
bfe58def1d10bfeaeb47f8bba2eb2a8ea208098cf894835b11d3f9283c292e6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 2, 2026.
Transparency log