Skip to main content

Vantage LiteLLM Callback

Required Vantage collector

The callback works with the Vantage LiteLLM collector. To set up the Vantage LiteLLM integration, install both components:

  1. Run the collector beside each LiteLLM proxy. The collector stores usage events and uploads compacted batches to Vantage.
  2. 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 (default 1024)
  • VANTAGE_COLLECTOR_RECOVERY_PROBE_SECONDS (default 5)
  • VANTAGE_COLLECTOR_GAP_EVENT_ID_SAMPLE_SIZE (default 32)
  • VANTAGE_COLLECTOR_GAP_SUMMARY_INTERVAL_SECONDS (default 60)
  • VANTAGE_COLLECTOR_SOCKET_PATH (default /var/run/vantage-collector/collector.sock)
  • VANTAGE_COLLECTOR_ACK_TIMEOUT_SECONDS (default 5)
  • VANTAGE_COLLECTOR_CONNECTION_POOL_SIZE (default 16)

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.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for vantage-litellm-callback 0.0.5
File Size Uploaded
vantage_litellm_callback-0.0.5.tar.gz 29.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for vantage-litellm-callback 0.0.5
File Interpreter ABI Platform
vantage_litellm_callback-0.0.5-py3-none-any.whl Python 3 none any Details

Total release size: 48.4 kB

Release files / vantage_litellm_callback-0.0.5.tar.gz

Download URL vantage_litellm_callback-0.0.5.tar.gz
Size 29.9 kB
Tags Source
SHA-256 checksum
How to use checksums
8b0fbeb57eb92f7682db85b6c3d78aa0c38f02019108eab109efabfae5fcd203
BLAKE2b-256 checksum
How to use checksums
bdfd74d4c6cb81ba8c07bbd8ac3e44ba013546938f09449098ab5773dd44e109
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 11, 2026.

Transparency log

Release files / vantage_litellm_callback-0.0.5-py3-none-any.whl

Download URL vantage_litellm_callback-0.0.5-py3-none-any.whl
Size 18.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ace7145b4bdf598a49e1a745d39e0cdde5af2d83c49807bf57c60e8f541822e7
BLAKE2b-256 checksum
How to use checksums
f941f003b781f5797d9466c9c15314eb24169a205d62d4efd539c10a5649ea5a
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 11, 2026.

Transparency log

Release history Release notifications | RSS feed

0.0.7

2 release files

0.0.6

2 release files

This release

0.0.5 This release

2 release files

0.0.4

2 release files

0.0.3

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page