atlasburn
See what each AI feature of your Python app spends, and stop runaway agent loops before they hit your bill.
atlasburn points your existing OpenAI, Anthropic or other OpenAI-compatible client at the
AtlasBurn Edge Proxy in one line. Every call is then
tracked by model and feature, and protected by the guardrails you set in AtlasBurn: alerts, throttling, and a
kill switch that pauses only the feature that is looping.
pip install atlasburn
Use it
Get a key at app.atlasburn.com (Settings → API keys) and set ATLASBURN_KEY.
import atlasburn
from openai import OpenAI
client = OpenAI(**atlasburn.openai_config(feature="support-chat"))
client.chat.completions.create(model="gpt-4o-mini", messages=[{"role": "user", "content": "Hi"}])
Anthropic:
from anthropic import Anthropic
client = Anthropic(**atlasburn.anthropic_config(feature="summarize"))
Tag a single call with a different feature:
client.chat.completions.create(..., extra_headers=atlasburn.feature("search"))
Every provider the proxy supports works with the OpenAI client: atlasburn.openai_config("gemini"), "cohere",
"openrouter", "mistral", "groq", "together", "deepseek", "xai". Pass that provider's own key as
api_key= to the client, exactly as before.
client = OpenAI(api_key=os.environ["GEMINI_API_KEY"], **atlasburn.openai_config("gemini"))
client.chat.completions.create(model="gemini-2.5-flash", messages=[{"role": "user", "content": "Hi"}])
Safe by default
- No dependencies. It only builds the client's
base_urland headers. - Never breaks your app. Without a key it warns and returns an empty config, so your client talks to the provider directly (untracked).
- Content-blind. AtlasBurn records usage (model, tokens, cost, timing, your feature label), not prompts or outputs.
What's next
This first release covers the proxy. A full Python SDK with automatic capture (no base-URL change, like the Node.js SDK) is in progress under this same package name.
Docs: Proxy quickstart · Guardrails and the kill switch · atlasburn.com
Apache-2.0 © 2026 AtlasBurn
Metadata
Release files for atlasburn 0.1.1
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 |
|---|---|---|---|---|
| atlasburn-0.1.1.tar.gz | 8.6 kB | Without provenance | Details for atlasburn-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| atlasburn-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for atlasburn-0.1.1-py3-none-any.whl |
Total release size: 16.8 kB
Release files / atlasburn-0.1.1.tar.gz
| Download URL | atlasburn-0.1.1.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea2ad8f9f780b7dbb510a40fca54ba05fb2619239b4be7fb38a24d220f7f3984
|
|
BLAKE2b-256 checksum How to use checksums |
36888e093e2b96a2b88c721b2fd1741d03ccf232c20c833b464eb2f258d50ed6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.9
|
Release files / atlasburn-0.1.1-py3-none-any.whl
| Download URL | atlasburn-0.1.1-py3-none-any.whl |
|---|---|
| Size | 8.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
028ddd760c41decf459c90fa668dd913d9d8551f2d9c473adecf9e43ecdef034
|
|
BLAKE2b-256 checksum How to use checksums |
1cb34d4f934e1d83bf79dcc001d9ab87eb2e3fc859f2d94f9a773c9c73a0026c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.9
|
Security for atlasburn 0.1.1
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.