Skip to main content

Budget: pre-flight cost caps, spend attribution, and circuit-breakers for LLM calls.

Project description

cendor-tokenguard

Stop runaway LLM bills, and get per-feature / per-user cost attribution for free. One decorator, one context manager. No dashboard, no account, no infra.

Caught a $40 runaway loop before it ran away — and told you which feature spent the rest.

PyPI license · pip install cendor-tokenguard

from cendor.core import instrument
from cendor.tokenguard import budget, track, report

client = instrument(openai_client)              # wrap once; tokenguard subscribes, never patches

@budget(usd=0.50, on_exceed="downgrade", downgrade={"gpt-4o": "gpt-4o-mini"})
def answer(q: str) -> str:
    with track(feature="support_bot", user_id="alice"):   # ambient attribution, zero bookkeeping
        resp = client.chat.completions.create(model="gpt-4o", messages=[{"role": "user", "content": q}])
        return resp.choices[0].message.content

for row in report(group_by=["feature", "user_id"]):       # where did the money go?
    print(row["tags"], row["usd"], row["calls"])

Highlights

  • Pre-flight circuit breakeron_exceed="block" raises before an over-budget call runs; "downgrade" reroutes to a cheaper model pre-flight; "truncate" degrades; "raise" stops a runaway loop; or call your own function.
  • Reasoning models, handled — you can't predict a thinking model's hidden reasoning pre-flight, so on_exceed="clamp" injects the provider's own token ceiling (max_completion_tokens/max_tokens) sized to the remaining budget — the call is capped server-side instead of overspending. report() breaks out reasoning_tokens, and the cumulative gate enforces on exact usage (which already includes reasoning). See docs/tokenguard.md → Reasoning models.
  • Decorator and context manager — budgets nest (an inner downgrade never masks an outer hard cap); config is validated at creation (a typo'd on_exceed or a map-less downgrade is a ValueError, never a silent no-op).
  • Cost attribution, freetrack(feature=…, user_id=…) tags ambient spend via contextvars (sync + async); report(group_by=[…]) shows where the money went, reasoning tokens included.
  • Cost as a test assertionreport().assert_under(usd=0.05, feature="search").
  • Pre-flight projectionestimate(model, messages) prices a call without making it.
  • Durable + bounded — pluggable use_sink(tokenguard.sinks.SQLiteSink / OTelSink); FIFO-bounded in-memory buffer (configure(max_records=…), dropped()). For long runs, wrap a durable sink in sinks.QueueSink(SQLiteSink(path)) so its I/O runs on a background thread and adds no per-call latencyflush()/close() guarantee durability at shutdown.
  • No silent USD blind spots — a call whose model isn't in the price table records $0, so a USD cap can't bite. tokenguard warns once per model (UnpricedModelWarning) and counts these in unpriced_calls() / report()'s unpriced_calls; configure(on_unpriced="raise") makes on_exceed="block" reject them. A token cap is unaffected — tokens are counted regardless of price.
  • Thread-safe, with one caveat — the spend buffer and SQLiteSink are lock-guarded for concurrent emits, but budgets/tags are ContextVar-based: asyncio tasks inherit them, a plain threading.Thread does not (carry them with contextvars.copy_context()).

Streaming timing — post-flight raise/truncate fire when a stream is consumed, not when it's launched (the call is accounted once the chunk iterator drains). A loop that launches many streams before draining them can overspend — drain each stream before the next, or use a pre-flight mode (block/downgrade/clamp), which is unaffected.

Wrap-around — it rides the call you already make. Offline and standalone — bundled prices, no account.

See docs/tokenguard.md · CHANGELOG. Part of the Cendor stack — github.com/cendorhq/cendor-libs. Powered by PowerAI Labs. Apache-2.0; provided "as is", without warranty — use at your own risk (LICENSE §7–8).

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

cendor_tokenguard-1.1.1.tar.gz (28.0 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

cendor_tokenguard-1.1.1-py3-none-any.whl (20.7 kB view details)

Uploaded Python 3

File details

Details for the file cendor_tokenguard-1.1.1.tar.gz.

File metadata

  • Download URL: cendor_tokenguard-1.1.1.tar.gz
  • Upload date:
  • Size: 28.0 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.12

File hashes

Hashes for cendor_tokenguard-1.1.1.tar.gz
Algorithm Hash digest
SHA256 aaca6d3686795dcae2cb7e2410e0eaf86a9967b68292e42e83db05083494d2cb
MD5 c1184388b62f32c03fb7389550e064f2
BLAKE2b-256 c8860522bd02edba46bbe74b5c50be1cf2dcf6fa90da008d3d06c352c1fca0ba

See more details on using hashes here.

Provenance

The following attestation bundles were made for cendor_tokenguard-1.1.1.tar.gz:

Publisher: release.yml on cendorhq/cendor-libs

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file cendor_tokenguard-1.1.1-py3-none-any.whl.

File metadata

File hashes

Hashes for cendor_tokenguard-1.1.1-py3-none-any.whl
Algorithm Hash digest
SHA256 07da659795009251c6fed67fc62437e2e0cd267c99f36ed7113dbe03f41d3bf0
MD5 f15bc548235b5490cd59faf50b6fe249
BLAKE2b-256 c89f79dc71d60827a4178d4e8d89135e4dfc896ed29a6946d64ca0b10006130f

See more details on using hashes here.

Provenance

The following attestation bundles were made for cendor_tokenguard-1.1.1-py3-none-any.whl:

Publisher: release.yml on cendorhq/cendor-libs

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page