open-batch-llm
A CLI tool to manage and run batch LLM calls.
Installation
pip install open-batch-llm
Or with uv:
uv tool install open-batch-llm
Usage
Validate a batch request file
open-batch-llm validate requests.json
Run batch requests (dry-run)
open-batch-llm run --dry-run requests.json
Run batch requests
open-batch-llm run requests.json --provider openai --model gpt-4o-mini --output results.json
Input file format
The input file must be a JSON array of request objects. Each object must contain a prompt key:
[
{"id": "req-1", "prompt": "What is 2 + 2?"},
{"id": "req-2", "prompt": "Name the planets of the solar system."}
]
Development
This project uses uv as the package manager and build system.
# Install dependencies
uv sync --all-groups
# Run tests
uv run pytest
# Build the package
uv build
Publishing
Releases are published to PyPI automatically via GitHub Actions when a new GitHub Release is created. The workflow uses Trusted Publishing (OIDC) — no API token is needed.
Metadata
Release files for open-batch-llm 0.1.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 | Provenance | Actions |
|---|---|---|---|---|
| open_batch_llm-0.1.0.tar.gz | 27.1 kB | With provenance | Details for open_batch_llm-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| open_batch_llm-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for open_batch_llm-0.1.0-py3-none-any.whl |
Total release size: 32.3 kB
Release files / open_batch_llm-0.1.0.tar.gz
| Download URL | open_batch_llm-0.1.0.tar.gz |
|---|---|
| Size | 27.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
165f98f411d159db7597d63f9e56a213f1f4e86a6d827719dd5e90323960a436
|
|
BLAKE2b-256 checksum How to use checksums |
b5e0fc2d356155dcd2a51a61667f5b0cccb21d556f4732f41481ca96ce6d1065
|
| 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 Apr 10, 2026.
Transparency logRelease files / open_batch_llm-0.1.0-py3-none-any.whl
| Download URL | open_batch_llm-0.1.0-py3-none-any.whl |
|---|---|
| Size | 5.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
66c2e58cdf91c78ddd2669a106f09d9301153f0575f07e8d08b40d9e0f96a422
|
|
BLAKE2b-256 checksum How to use checksums |
c3b84c352066bb4307f49fe317ba0b2eedf8a8ec679fb108aa0a107504e91412
|
| 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 Apr 10, 2026.
Transparency logSecurity for open-batch-llm 0.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for open_batch_llm-0.1.0.tar.gz
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 Apr 10, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.