llmtrim-uniffi
UniFFI bindings over llmtrim-core: one Rust
definition, idiomatic in-process bindings for Python, Ruby, Swift and Kotlin. The
compression runs natively in the caller's process (no server, no async).
API
A deliberately flat surface over the engine:
fn compress(
input: String, // a provider-shaped request body (JSON)
provider: Option<Provider>, // OpenAi | Anthropic | Google, or None to auto-detect
preset: Option<String>, // "aggressive" | "agent" | "code" | "rag" | "safe" | …
// None = config from the environment / config file
) -> Result<CompressOutput, LlmtrimError>
CompressOutput carries the compressed request_json, the resolved provider/model,
the tokenizer label/exactness, and the before/after/frozen input-token counts. Embedders
that need the full rehydration plan or per-stage reports should depend on llmtrim-core
directly in Rust.
In-process vs. the proxy
llmtrim has two integration routes:
- The proxy (
HTTPS_PROXY=127.0.0.1:8788 llmtrim) intercepts your existing traffic and compresses it in flight. Nothing in your code changes, but the client has to route through the proxy and trust its CA. - These bindings compress in your process. You call
compress()on the request body, then send the result with your own HTTP client. No proxy, no CA, no env-var setup.
Use the in-process path when the proxy can't run:
- Sandboxed / serverless functions where you can't set a process-wide
HTTPS_PROXYor run a side process. - Certificate-pinned clients that reject a MITM CA, so the proxy's interception fails.
- Anywhere you'd rather not add a network hop or an extra moving part.
It replaces a per-framework adapter: instead of wiring a hook into each SDK, you compress
the body once and POST it yourself. Runnable end-to-end examples (compress, then send with
your own client) are in examples/.
Python
# Build a self-contained wheel (cdylib + generated glue):
crates/llmtrim-uniffi/scripts/build-wheel.sh --release
pip install target/wheels/llmtrim-*.whl
import llmtrim, json
req = json.dumps({"model": "gpt-4o",
"messages": [{"role": "user", "content": "…"}]})
out = llmtrim.compress(req, llmtrim.Provider.OPEN_AI, "aggressive")
print(out.input_tokens_before, "->", out.input_tokens_after)
# send out.request_json to the provider
Why
build-wheel.shand not plainmaturin build: maturin'sbindings = "uniffi"auto-packaging is sensitive to the maturin↔uniffi version pair. With maturin 1.14 + uniffi 0.31 it builds the native library into the wheel but omits the generated Python glue (empty package__init__.py). The script runs maturin, then injects the freshly generated bindings and repacks the wheel with valid RECORD hashes. Remove it once the auto path packages cleanly.
Ruby / Swift / Kotlin
All targets generate from the same built library, no extra Rust. The generated glue is a build artifact (its checksums are pinned to the library ABI), so it is regenerated per release rather than committed:
crates/llmtrim-uniffi/scripts/generate-bindings.sh out/ # python, ruby, swift, kotlin
Generation needs an unstripped library. Library-mode
uniffi-bindgenreads metadata symbols from the cdylib, but the workspace release profile setsstrip = true. The script therefore generates from the (unstripped) debug build; the native library you ship can be a strippedcargo build --release -p llmtrim-unifficdylib; the glue loads it by name.
Ruby (verified). This is the raw generated binding (module LlmtrimFfi), for a
source build with libllmtrim_ffi.so on the load path. The published gem aliases it to
Llmtrim (require "llmtrim" then Llmtrim.compress(...)); see
packaging/ruby.
require_relative "llmtrim_ffi"
require "json"
out = LlmtrimFfi.compress(
JSON.generate({model: "gpt-4o", messages: [{role: "user", content: "…"}]}),
LlmtrimFfi::Provider::OPEN_AI, "aggressive")
puts "#{out.input_tokens_before} -> #{out.input_tokens_after}"
Swift emits llmtrim_ffi.swift + an FFI header and modulemap; Kotlin emits
uniffi/.../llmtrim_ffi.kt (which loads the cdylib via JNA). CI compiles and runs a smoke
for both: Swift on macOS (swiftc against the modulemap), Kotlin on a JVM (kotlinc +
JNA), so a binding break is caught in all four languages (see tests/swift, tests/kotlin
and the bindings* jobs in .github/workflows/ci.yml).
Publishable packages
Each ships the compiled engine bundled, so consumers need no Rust toolchain:
| Target | Build | Package | Verified |
|---|---|---|---|
| Python (PyPI) | scripts/build-wheel.sh |
wheel | locally |
| Ruby (gem) | scripts/build-gem.sh |
packaging/ruby/ |
locally |
| Kotlin/JVM (Maven) | scripts/build-maven.sh |
packaging/kotlin/ |
locally |
| Swift (SwiftPM) | scripts/build-xcframework.sh |
packaging/swift/ |
macOS CI only |
Each packaging/<lang>/README.md has the usage + publish details.
1 maintainer
Metadata
1 maintainer
Release files for llmtrim 0.13.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| llmtrim-0.13.4-py3-none-win_amd64.whl | Python 3 | none | Windows x86-64 | Details |
| llmtrim-0.13.4-py3-none-manylinux_2_34_x86_64.whl | Python 3 | none | Linux glibc 2.34+ x86-64 | Details |
| llmtrim-0.13.4-py3-none-manylinux_2_34_aarch64.whl | Python 3 | none | Linux glibc 2.34+ ARM64 | Details |
| llmtrim-0.13.4-py3-none-macosx_11_0_arm64.whl | Python 3 | none | macOS 11.0+ ARM64 | Details |
| llmtrim-0.13.4-py3-none-macosx_10_12_x86_64.whl | Python 3 | none | macOS 10.12+ x86-64 | Details |
Total release size: 41.0 MB
Release files / llmtrim-0.13.4-py3-none-win_amd64.whl
| Download URL | llmtrim-0.13.4-py3-none-win_amd64.whl |
|---|---|
| Size | 8.0 MB |
| Tags | Python 3 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
8626407cb3371fd5dc4bc3a50d39243cfe05835d1bc6cc191b141c6069273038
|
|
BLAKE2b-256 checksum How to use checksums |
6cf5fa40b5b7989d6cb147573cb72977151a1a96af22820935c1e1eb2a030bbf
|
| 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 8, 2026.
Transparency logRelease files / llmtrim-0.13.4-py3-none-manylinux_2_34_x86_64.whl
| Download URL | llmtrim-0.13.4-py3-none-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 8.5 MB |
| Tags | Linux glibc 2.34+ x86-64 Python 3 |
|
SHA-256 checksum How to use checksums |
b063d0abce9e257fdc987522da1ef34290da369db251519e1cdd68df7624549d
|
|
BLAKE2b-256 checksum How to use checksums |
b440a14becabba0afd6c66ed8b7daafec208fee57329df7c0b2ea4149ccca037
|
| 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 8, 2026.
Transparency logRelease files / llmtrim-0.13.4-py3-none-manylinux_2_34_aarch64.whl
| Download URL | llmtrim-0.13.4-py3-none-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 8.4 MB |
| Tags | Linux glibc 2.34+ ARM64 Python 3 |
|
SHA-256 checksum How to use checksums |
99be5acec1763615cfbc09b11ca4b27912602ff32c8c57abe0c654245ef0fa9f
|
|
BLAKE2b-256 checksum How to use checksums |
5d13a09bdeeb313389a2b926c7033ccc1db551ec3d212d92a59200ba4bb1caf6
|
| 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 8, 2026.
Transparency logRelease files / llmtrim-0.13.4-py3-none-macosx_11_0_arm64.whl
| Download URL | llmtrim-0.13.4-py3-none-macosx_11_0_arm64.whl |
|---|---|
| Size | 8.0 MB |
| Tags | Python 3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
3af997d4960ad0ef4c4578345c7f988be89a5165316438855d70d2e43f3ad152
|
|
BLAKE2b-256 checksum How to use checksums |
ab87fea1b7a769164e9798da92f4ed8407b45d146242fdc6be6f8151f53ecc19
|
| 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 8, 2026.
Transparency logRelease files / llmtrim-0.13.4-py3-none-macosx_10_12_x86_64.whl
| Download URL | llmtrim-0.13.4-py3-none-macosx_10_12_x86_64.whl |
|---|---|
| Size | 7.9 MB |
| Tags | Python 3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
3c5db91f840d8677adfa0ad6f1c7182c57dc64a07bf3f17e278aa5084ca7dea9
|
|
BLAKE2b-256 checksum How to use checksums |
2c81cd46509327a20714346026db712ffd3593f9a01bc21764dfd86f4f5baabf
|
| 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 8, 2026.
Transparency log
