Vantage LiteLLM Callback
Required Vantage collector
The callback works with the Vantage LiteLLM collector. To set up the Vantage LiteLLM integration, install both components:
- Run the collector beside each LiteLLM proxy. The collector stores usage events and uploads compacted batches to Vantage.
- Install this callback in the LiteLLM Python environment. The callback sends usage events to the local collector over its Unix socket.
The callback cannot upload usage to Vantage by itself. The collector cannot collect LiteLLM usage without the callback. See the collector repository README for deployment and configuration instructions.
Install
Install a released version with:
pip install vantage-litellm-callback
To work from a source checkout, install this directory with pip install ..
Configure LiteLLM with:
litellm_settings:
callbacks:
- vantage_callback.callback_instance
See the repository README for collector setup and lifecycle billing semantics.
The callback is fail-open: collector outages, acknowledgement failures, malformed
responses, queue pressure, and projection errors never block or fail a provider
request. Usage events are placed into a bounded in-process queue and delivered by
a background worker. When delivery is unhealthy, the worker opens a circuit,
aggregates bounded loss information, and periodically probes the collector with a
versioned delivery_gap control frame. Normal delivery resumes only after that
frame receives a durable acknowledgement.
Configuration:
VANTAGE_COLLECTOR_DELIVERY_QUEUE_SIZE(default1024)VANTAGE_COLLECTOR_RECOVERY_PROBE_SECONDS(default5)VANTAGE_COLLECTOR_GAP_EVENT_ID_SAMPLE_SIZE(default32)VANTAGE_COLLECTOR_GAP_SUMMARY_INTERVAL_SECONDS(default60)VANTAGE_COLLECTOR_SOCKET_PATH(default/var/run/vantage-collector/collector.sock)VANTAGE_COLLECTOR_ACK_TIMEOUT_SECONDS(default5)VANTAGE_COLLECTOR_CONNECTION_POOL_SIZE(default16)
The queue and gap aggregate are intentionally process-local and bounded. A process exit may therefore lose queued events; the gap frame reports losses observed while the process remains alive.
Metadata
Release files for vantage-litellm-callback 0.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| vantage_litellm_callback-0.0.6.tar.gz | 28.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vantage_litellm_callback-0.0.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 46.5 kB
Release files / vantage_litellm_callback-0.0.6.tar.gz
| Download URL | vantage_litellm_callback-0.0.6.tar.gz |
|---|---|
| Size | 28.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e7102aafff0d88871f330d2d45f59f31d9d7e609330d8090fc12d46e40ffb372
|
|
BLAKE2b-256 checksum How to use checksums |
02c0fc13d93adb630675931eb6317665f97e16c59b95b27027ee728a2f8c6f5d
|
| 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 23, 2026.
Transparency logRelease files / vantage_litellm_callback-0.0.6-py3-none-any.whl
| Download URL | vantage_litellm_callback-0.0.6-py3-none-any.whl |
|---|---|
| Size | 17.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a4132a05a12b409edefb5e9c70ef3f48ac906ecca6f6928a60aa722a863a2626
|
|
BLAKE2b-256 checksum How to use checksums |
e968b39c491255cecea0ac6f4b4a0eda7b0fc419732590f96897c27f0456b48c
|
| 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 23, 2026.
Transparency log