kazenai

Stop your AI agents from burning your budget. Catch loops before they catch you.

Install: PyPI · kazenai · Customer SDK: kazenai-finops · Products: kazenai.com

What is this?

kazenai is the core Python SDK behind KazenAI’s economic control layer for AI agents. One call — monitor() — wraps your OpenAI or Anthropic client and:

1. Blocks overspend before the provider call (BudgetExceeded)
2. Detects runaway loops before another LLM request
3. Optionally ships evidence to Agent FinOps / Agent Lens as canonical KazenEvents

Most observability tools tell you what went wrong after the bill. KazenAI can stop the call that would cause it.

Traditional tools:  LLM call → response → log cost → dashboard shows overspend
KazenAI:            Pre-flight check → BLOCKED → LLM call never made

Install

python -m pip install kazenai openai
# Most teams install the customer package instead:
python -m pip install kazenai-finops openai

kazenai-finops re-exports this SDK and is the recommended install for product integrations.

Requires Python 3.10+.

Quick start

import os
from openai import OpenAI
from kazenai import monitor, BudgetExceeded

# Optional FinOps ingest (env only — not monitor kwargs):
#   export KAZENAI_FINOPS_API_KEY=kz_...
#   export KAZENAI_FINOPS_INGEST_URL=https://finops.example.com

client = monitor(
    OpenAI(),
    agent_id="support-agent",
    max_budget_usd=5.00,
    debug=True,
)

try:
    client.chat.completions.create(
        model="gpt-4o-mini",
        messages=[{"role": "user", "content": "hello"}],
    )
except BudgetExceeded as e:
    print("hard budget cap:", e)

Your call sites stay the same — monitor() wraps the client.

With debug=True you’ll see spend as the run progresses:

[KazenAI] step=1  gpt-4o-mini  cost=$0.0043  total=$0.0043  proj=$0.21/$5.00  OK
[KazenAI] step=8  gpt-4o-mini  cost=$0.0039  total=$0.43    proj=$4.91/$5.00  WARN:budget_87pct
[KazenAI] step=9  gpt-4o-mini  BLOCKED:budget  spent=$5.00  limit=$5.00

Illustrative debug output — not a customer bill or savings claim.

What you get

Supported today

Why local enforcement matters

• Hard cap works without FinOps network — deny even when ingest is offline
• Low overhead — budget and loop checks stay on the hot path
• Backend outage ≠ unprotected spend on the local hard-cap path

Optional FinOps environment variables

Packages in the stack

Contributing

Issues and PRs that improve budget/loop reliability are welcome. Keep claims aligned with the supported paths above.

Products and design-partner enquiries: kazenai.com · founder@kazenai.com

License

Apache License 2.0. See LICENSE and NOTICE.