AgentBill Python SDK
OpenTelemetry-based SDK for automatically tracking and billing AI agent usage.
Installation
From PyPI (Recommended)
pip install agentbill-py-sdk
From PyPI (Coming Soon)
pip install agentbill
From Source
# Clone your repository and install
git clone https://github.com/yourusername/agentbill-python-sdk.git
cd agentbill-python-sdk
pip install -e .
File Structure
agentbill-python/
├── agentbill/
│ ├── __init__.py
│ ├── client.py
│ ├── tracer.py
│ └── types.py
├── examples/
│ ├── openai_basic.py
│ ├── anthropic_basic.py
│ ├── bedrock_basic.py
│ ├── azure_openai_basic.py
│ ├── mistral_basic.py
│ └── google_ai_basic.py
├── tests/
│ ├── test_agentbill.py
│ └── test_tracer.py
├── README.md
├── setup.py
├── pyproject.toml
├── pytest.ini
├── Makefile
├── CHANGELOG.md
├── CONTRIBUTING.md
├── SECURITY.md
└── LICENSE
Quick Start
from agentbill import AgentBill
import openai
# Initialize AgentBill
agentbill = AgentBill.init({
"api_key": "your-api-key",
"customer_id": "customer-123",
"debug": True
})
# Wrap your OpenAI client
client = agentbill.wrap_openai(openai.OpenAI(
api_key="sk-..."
))
# Use normally - all calls are automatically tracked!
response = client.chat.completions.create(
model="gpt-4",
messages=[{"role": "user", "content": "Hello!"}]
)
⚠️ Critical: Cost Guard Error Handling
When using budget limits (daily_budget/monthly_budget), the SDK raises exceptions when limits are exceeded. Do NOT catch and continue with direct AI calls - the blocking is intentional to prevent overspending!
# ❌ WRONG - This bypasses budget protection!
try:
response = wrapped_client.chat.completions.create(...)
except Exception as e:
print("AgentBill failed, continuing anyway...")
response = unwrapped_client.chat.completions.create(...) # BUDGET BYPASSED!
# ✅ CORRECT - Respect the block, handle gracefully
try:
response = wrapped_client.chat.completions.create(...)
except Exception as e:
if hasattr(e, 'code') and e.code == 'BUDGET_EXCEEDED':
print("Budget limit reached - please upgrade or wait")
return None # Return early, don't bypass!
raise # Re-raise other errors
Features
- ✅ Zero-config instrumentation
- ✅ Accurate token & cost tracking
- ✅ Multi-provider support (OpenAI, Anthropic, Bedrock, Azure OpenAI, Mistral, Google AI)
- ✅ Rich metadata capture
- ✅ OpenTelemetry-based
- ✅ Cost Guard budget enforcement (blocks requests BEFORE spending)
Supported Providers
- OpenAI - GPT-4, GPT-5, Embeddings, DALL-E, Whisper, TTS
- Anthropic - Claude Sonnet, Claude Opus
- AWS Bedrock - Claude, Titan, and other Bedrock models
- Azure OpenAI - GPT models via Azure
- Mistral AI - Mistral models
- Google AI - Gemini Pro, Gemini Flash
Provider Examples
OpenAI
from agentbill import AgentBill
import openai
agentbill = AgentBill.init({"api_key": "your-api-key"})
client = agentbill.wrap_openai(openai.OpenAI(api_key="sk-..."))
response = client.chat.completions.create(
model="gpt-4",
messages=[{"role": "user", "content": "Hello!"}]
)
Anthropic
from agentbill import AgentBill
import anthropic
agentbill = AgentBill.init({"api_key": "your-api-key"})
client = agentbill.wrap_anthropic(anthropic.Anthropic(api_key="sk-ant-..."))
response = client.messages.create(
model="claude-sonnet-4-20250514",
max_tokens=1024,
messages=[{"role": "user", "content": "Hello!"}]
)
AWS Bedrock
from agentbill import AgentBill
import boto3
agentbill = AgentBill.init({"api_key": "your-api-key"})
bedrock = agentbill.wrap_bedrock(boto3.client('bedrock-runtime'))
response = bedrock.invoke_model(
modelId='anthropic.claude-v2',
body=json.dumps({
"prompt": "Hello!",
"max_tokens_to_sample": 300
})
)
Azure OpenAI
from agentbill import AgentBill
from openai import AzureOpenAI
agentbill = AgentBill.init({"api_key": "your-api-key"})
client = agentbill.wrap_azure_openai(AzureOpenAI(
api_key="your-azure-key",
api_version="2024-02-01",
azure_endpoint="https://your-resource.openai.azure.com"
))
response = client.chat.completions.create(
model="gpt-4",
messages=[{"role": "user", "content": "Hello!"}]
)
Mistral AI
from agentbill import AgentBill
from mistralai import Mistral
agentbill = AgentBill.init({"api_key": "your-api-key"})
client = agentbill.wrap_mistral(Mistral(api_key="your-mistral-key"))
response = client.chat.complete(
model="mistral-large-latest",
messages=[{"role": "user", "content": "Hello!"}]
)
Google AI (Gemini)
from agentbill import AgentBill
import google.generativeai as genai
agentbill = AgentBill.init({"api_key": "your-api-key"})
genai.configure(api_key="your-google-key")
model = genai.GenerativeModel('gemini-pro')
wrapped_model = agentbill.wrap_google_ai(model)
response = wrapped_model.generate_content("Hello!")
Configuration
config = {
"api_key": "your-api-key", # Required
"base_url": "https://...", # Optional
"customer_id": "customer-123", # Optional
"debug": True # Optional
}
agentbill = AgentBill.init(config)
Publishing to PyPI
Prerequisites
- Create a PyPI account at https://pypi.org/account/register/
- Generate an API token at https://pypi.org/manage/account/token/
- Create
~/.pypircfile with your token:
[pypi]
username = __token__
password = pypi-YOUR_API_TOKEN_HERE
Publishing Steps
# Build the package
python setup.py sdist bdist_wheel
# Upload to PyPI
pip install twine
twine upload dist/*
GitHub Repository Setup
- Create your GitHub repository (e.g.,
agentbill-python-sdk) - Push all files (agentbill/, examples/, LICENSE, setup.py, README.md)
- Tag releases:
git tag v1.0.0 && git push origin v1.0.0 - Users can install with:
pip install agentbill-py-sdk
Idempotent Ingestion (X-Request-Id)
Every OTLP batch this SDK exports to /functions/v1/otel-collector carries an
X-Request-Id: <uuid4> header (auto-generated per export, reused across
transport-level retries within that export). The collector deduplicates on
(company_id, request_id), so a transient 5xx / network retry will not
double-write WAL rows, spans, or billing events.
- No configuration required — the header is emitted automatically by the v7.x line of this SDK.
- Server fallback: clients that cannot set custom headers may send
{"requestId": "..."}at the JSON envelope root. - Native OTLP exporters: the standard OTLP-HTTP exporter keeps headers
static across batches, so per-batch rotation is not yet wired on that path
(
PHASE3-R3-SDK-REQUESTID-NATIVE— tracked); the collector still dedupes those payloads on the natural key(company_id, trace_id, span_id).
See the OpenTelemetry Integration docs for the full request-id contract.
License
MIT
Metadata
Release files for agentbill-py-sdk 11.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| agentbill_py_sdk-11.0.2.tar.gz | 78.8 kB | Without provenance | Details for agentbill_py_sdk-11.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agentbill_py_sdk-11.0.2-py3-none-any.whl | Python 3 | none | any | Details for agentbill_py_sdk-11.0.2-py3-none-any.whl |
Total release size: 170.7 kB
Release files / agentbill_py_sdk-11.0.2.tar.gz
| Download URL | agentbill_py_sdk-11.0.2.tar.gz |
|---|---|
| Size | 78.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
925998d4bea7c85f5ed8f19f8d13bbe03e09c2f22942c8408c2e4962b807dd6d
|
|
BLAKE2b-256 checksum How to use checksums |
056cc259e8a63ae19a62ff0400c04f6e31e9d7db00acb030394b62a2788726dd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Release files / agentbill_py_sdk-11.0.2-py3-none-any.whl
| Download URL | agentbill_py_sdk-11.0.2-py3-none-any.whl |
|---|---|
| Size | 91.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
07d6f94357f5e8daf8a18752d80e8694c712e276635e0ff7ca1439d8c306c10c
|
|
BLAKE2b-256 checksum How to use checksums |
a4e3f5abb393cb85fa3a019f0457ec56de2210888988a729865a3b8380475bb0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.15
|
Security for agentbill-py-sdk 11.0.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.