jammi-client
Pure-Python gRPC client for a remote Jammi engine — the deploy half of the develop→deploy journey.
jammi-ai runs an embedded engine in-process and bundles this client for its
remote targets. jammi-client is the lean variant: a universal
py3-none-any wheel that links no candle/ML stack — just grpcio + protobuf
pyarrow— for production where the engine runs behind a server.
One front door
import jammi_client
db = jammi_client.connect("https://engine.example.com")
db.add_source("patents", url="s3://corpus/patents.parquet", format="parquet")
db.generate_embeddings(source="patents", model="local:tiny_bert",
columns=["abstract"], key="id", modality="text")
q = db.encode_query(model="local:tiny_bert", query="quantum computing")
hits = db.search("patents", query=q, k=5) # -> pyarrow.Table
connect(target) is the Python mirror of the Rust Jammi::open(Target):
transport is config, not a code path.
Authenticated channels
A bearer-protected endpoint is reached by attaching credentials to the channel — the bearer rides the channel (attached once at connect), not threaded through every call:
from jammi_client import connect, BearerCredentials
db = connect("https://engine.example.com", credentials=BearerCredentials(token))
The same works on a plaintext grpc:// target for local development. The
channel-level bearer covers the typed gRPC verbs; db.sql() (the Flight SQL
lane) does not yet carry it — tracked at
issue #96.
| target | transport |
|---|---|
https://host / grpcs://host:8081 |
secure remote |
http://host / grpc://host:8081 |
plaintext remote |
file:///data |
local engine — not in this build; raises NoEmbeddedEngineError pointing at pip install jammi-ai |
Scaling local→remote is an env flip (connect(os.environ["JAMMI_TARGET"]))
with no code change. Productionising from the embed wheel to this lean client is
a one-line import swap (import jammi_ai → import jammi_client), connect
unchanged.
Generated from the canonical proto
The wire stubs under jammi_client/_generated/ are generated from the same
jammi.v1 proto the engine, npm client, and embed wheel speak — one source, no
parallel schema. Regenerate after a proto change:
pip install -e '.[dev]'
make generate
1 maintainer
Metadata
1 maintainer
Release files for jammi-client 0.33.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| jammi_client-0.33.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / jammi_client-0.33.0-py3-none-any.whl
| Download URL | jammi_client-0.33.0-py3-none-any.whl |
|---|---|
| Size | 121.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e7720bb70affd6eaa57752a35f4c10d41a708075224bf0b8ff3746861e4f3aa5
|
|
BLAKE2b-256 checksum How to use checksums |
27253634c6afc227373bcc97561f10a04b7240598fb32c7726a43991169c7e35
|
| 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 4, 2026.
Transparency log
