zexl 0.1.0__tar.gz

zexl-0.1.0/.gitignore

@@ -0,0 +1,29 @@
+# Python
+__pycache__/
+*.py[cod]
+.venv/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+dist/
+*.egg-info/
+
+# Node
+node_modules/
+.next/
+out/
+*.tsbuildinfo
+next-env.d.ts
+
+# Secrets and local config
+.env
+.env.*
+!.env.example
+
+# OS / editor
+.DS_Store
+.idea/
+.vscode/
+
+# Database backups (scripts/backup-restore-check.sh)
+backups/

zexl-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "{}"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright {yyyy} {name of copyright owner}
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+

zexl-0.1.0/PKG-INFO

@@ -0,0 +1,177 @@
+Metadata-Version: 2.5
+Name: zexl
+Version: 0.1.0
+Summary: See how much of your AI spend did useful work, without sending a single prompt.
+Project-URL: Homepage, https://tryzexl.xyz
+Author: Zexl
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: ai,anthropic,cost,llm,observability,openai
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Typing :: Typed
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+
+# zexl (Python SDK)
+
+Shows how much of your AI spend did useful work. It records metadata about each model call and sends it to Zexl. **Prompt and response text never leave your process.**
+
+Status: early release (0.1.0). Tested against mocked provider responses only; not yet run against live provider APIs.
+
+## Install and use
+
+```bash
+pip install zexl
+```
+
+```bash
+export ZEXL_API_KEY="zx_<id>_<secret>.<salt>"
+```
+
+```python
+import zexl.auto  # add once, at your application's entry point
+```
+
+That is the whole setup. Calls made through the `openai` and `anthropic` packages are recorded from then on.
+
+Optional:
+
+```python
+import zexl
+
+zexl.set_customer("acct_123")  # attribute spend to one of your customers (use an id)
+
+with zexl.run("research"):  # group calls into one run explicitly
+    ...
+
+
+@zexl.run()  # or as a decorator
+def summarise(doc): ...
+
+
+with zexl.feature("checkout-bot"):  # set the feature label without starting a run
+    ...
+
+zexl.flush()  # before a short-lived process (serverless) exits
+```
+
+| Environment variable | Meaning | Default |
+|---|---|---|
+| `ZEXL_API_KEY` | Your key. Required | none |
+| `ZEXL_ENV` | Environment tag for every call | `production` |
+| `ZEXL_DISABLED` | `1` turns the SDK off completely | off |
+| `ZEXL_ENDPOINT` | Intake URL | Zexl's hosted intake |
+| `ZEXL_OPENAI_STREAM_USAGE` | `1` asks OpenAI for token usage on streamed chat completions (see below) | off |
+
+## What leaves your process
+
+Everything the SDK sends is built from a fixed allowlist (`src/zexl/_export.py`, `SCHEMA`). This is the complete list:
+
+| Sent | Examples |
+|---|---|
+| Provider, API and model names | `openai`, `chat`, `gpt-4o` |
+| Token counts reported by the provider | input, output, cache read, cache write, reasoning |
+| Character counts | system prompt, tool definitions, input, output |
+| Timings | start, end, time to first token |
+| Outcome | finish reason, HTTP status, exception class name, whether a stream completed |
+| Tool names | the `name` of each tool the model called, and how many tools were defined |
+| Salted hashes | of the request, system prompt, tool definitions, newest input, output, and each tool call |
+| Run id and step number | generated locally |
+| Labels you set | feature, customer, environment |
+| SDK details | SDK version, and an 8-character check value derived from your salt |
+
+Never sent: message text, system prompts, tool descriptions and schemas, tool arguments, tool results, model output, images, exception messages, your provider API keys, and the salt.
+
+Things to know:
+
+- **Tool names and model names are sent as-is** when they look like identifiers. Do not put secrets in tool names.
+- **The feature label defaults to `module.function`** of the code that made the call. Set it yourself with `zexl.feature()` if your function names are sensitive.
+- **Lengths are sent.** Character and token counts reveal how long a prompt was, not what it said.
+
+### How the hashes work
+
+The part of your key after the dot is a salt. It stays in your process and is never transmitted. Every hash is an HMAC-SHA256 keyed with that salt, cut to 128 bits. Without the salt a hash cannot be matched to text, including by Zexl, and hashes from different workspaces cannot be compared. If you lose the key, the salt cannot be recovered; a new salt starts a new hash history.
+
+### How this is tested
+
+`tests/test_leak.py` plants canary strings in every place content can appear (system prompt, messages, images, tool definitions, tool arguments, tool results, responses, streamed chunks, error bodies), runs each supported call style, and fails if a canary or the salt appears in any byte the SDK sends. It also plants a deliberate leak to confirm the check would catch one.
+
+## Behaviour you can rely on
+
+- **Your calls are never blocked or changed.** Capture runs around the provider call; delivery happens on a background thread. If Zexl's intake is down, records are dropped and your application carries on.
+- **Errors inside the SDK never reach your code.** They are logged once on the `zexl` logger at warning level.
+- **Exceptions from the provider pass through untouched.**
+- **Bounded memory.** At most 2,048 records wait for delivery; beyond that the SDK drops records.
+- **Delivery is tried, not guaranteed.** Records go out every 2 seconds or every 256 records. A send that times out, loses its connection, or gets a 429 or 5xx is tried once more after 1 second. If that also fails, the batch is dropped and the SDK waits before the next send, from 2 seconds up to 60 seconds while the outage lasts.
+- **No dependencies.** The SDK uses only the Python standard library.
+
+`zexl.status()` reports whether capture is on, which hooks are active, and how many records were sent or dropped.
+
+## Overhead
+
+Measured with `bench/overhead.py` on a laptop (Python 3.12, 14 Nov 2026). The provider is a
+mock inside the process, so these figures are the SDK's own work, not network time.
+
+| Call | Time added per call (median) |
+|---|---|
+| Chat or messages call, 1 KB prompt | 0.05 ms |
+| Async chat call, 1 KB prompt | 0.05 ms |
+| Streamed chat call, 200 chunks | 0.32 ms for the whole stream |
+| Agent step, 60 KB history and 10 tools | 0.23 ms |
+| Agent step, 1 MB history | 1.4 ms |
+
+Memory: a process that made 5,000 agent-step calls peaked 12 MB higher with the SDK on, and
+16 MB higher when the intake was down the whole time. The queue holds at most 2,048 records;
+beyond that the SDK drops records, so memory does not keep growing.
+
+Sending happens on a background thread and never delays your call.
+
+## What is recorded
+
+| Provider | Covered |
+|---|---|
+| OpenAI | `chat.completions.create`, `.parse`, `.stream`; `responses.create`, `.parse`; streaming; `with_raw_response`; sync and async |
+| Anthropic | `messages.create`, `.parse`, `.stream`; `beta.messages`; streaming; `with_raw_response`; sync and async |
+
+Tested with `openai` 1.68 to 3.50 and `anthropic` 0.50 to 2.8, on Python 3.10 and 3.13.
+
+Known limits:
+
+- **Streamed OpenAI chat completions report no token usage** unless you pass `stream_options={"include_usage": True}`. Without it Zexl estimates cost from character counts. Setting `ZEXL_OPENAI_STREAM_USAGE=1` adds the option for you; it makes OpenAI send one extra final chunk with an empty `choices` list, so check your stream-handling code first.
+- **`with_streaming_response` calls are recorded without response details**, because the SDK does not read the body ahead of you.
+- **Retries inside the provider SDK are invisible.** A call that succeeded on its third attempt is one record.
+- **Not yet covered:** the Bedrock, Vertex and Azure client variants are untested, and other providers and agent frameworks are not hooked.
+
+### Runs
+
+A run is one unit of agent work. Without any code from you, the SDK groups calls into a run when each request continues the previous response (the usual agent loop), or uses `previous_response_id`. If your application already has an OpenTelemetry trace active, the trace is the run.
+
+Automatic grouping does not work when your agent trims or summarises its message history, or for sub-agents with their own conversations: those appear as separate runs. Wrap the work in `zexl.run()` to group it.
+
+## Development
+
+```bash
+uv sync
+```
+
+```bash
+uv run ruff check . && uv run ruff format --check . && uv run mypy && uv run pytest
+```
+
+Measure what the SDK adds to a call (time per call, peak memory), against a mock provider:
+
+```bash
+uv run python bench/overhead.py
+```
+
+Test against several provider SDK versions (from the repository root):
+
+```bash
+scripts/sdk-matrix.sh
+```

zexl-0.1.0/README.md

@@ -0,0 +1,157 @@
+# zexl (Python SDK)
+
+Shows how much of your AI spend did useful work. It records metadata about each model call and sends it to Zexl. **Prompt and response text never leave your process.**
+
+Status: early release (0.1.0). Tested against mocked provider responses only; not yet run against live provider APIs.
+
+## Install and use
+
+```bash
+pip install zexl
+```
+
+```bash
+export ZEXL_API_KEY="zx_<id>_<secret>.<salt>"
+```
+
+```python
+import zexl.auto  # add once, at your application's entry point
+```
+
+That is the whole setup. Calls made through the `openai` and `anthropic` packages are recorded from then on.
+
+Optional:
+
+```python
+import zexl
+
+zexl.set_customer("acct_123")  # attribute spend to one of your customers (use an id)
+
+with zexl.run("research"):  # group calls into one run explicitly
+    ...
+
+
+@zexl.run()  # or as a decorator
+def summarise(doc): ...
+
+
+with zexl.feature("checkout-bot"):  # set the feature label without starting a run
+    ...
+
+zexl.flush()  # before a short-lived process (serverless) exits
+```
+
+| Environment variable | Meaning | Default |
+|---|---|---|
+| `ZEXL_API_KEY` | Your key. Required | none |
+| `ZEXL_ENV` | Environment tag for every call | `production` |
+| `ZEXL_DISABLED` | `1` turns the SDK off completely | off |
+| `ZEXL_ENDPOINT` | Intake URL | Zexl's hosted intake |
+| `ZEXL_OPENAI_STREAM_USAGE` | `1` asks OpenAI for token usage on streamed chat completions (see below) | off |
+
+## What leaves your process
+
+Everything the SDK sends is built from a fixed allowlist (`src/zexl/_export.py`, `SCHEMA`). This is the complete list:
+
+| Sent | Examples |
+|---|---|
+| Provider, API and model names | `openai`, `chat`, `gpt-4o` |
+| Token counts reported by the provider | input, output, cache read, cache write, reasoning |
+| Character counts | system prompt, tool definitions, input, output |
+| Timings | start, end, time to first token |
+| Outcome | finish reason, HTTP status, exception class name, whether a stream completed |
+| Tool names | the `name` of each tool the model called, and how many tools were defined |
+| Salted hashes | of the request, system prompt, tool definitions, newest input, output, and each tool call |
+| Run id and step number | generated locally |
+| Labels you set | feature, customer, environment |
+| SDK details | SDK version, and an 8-character check value derived from your salt |
+
+Never sent: message text, system prompts, tool descriptions and schemas, tool arguments, tool results, model output, images, exception messages, your provider API keys, and the salt.
+
+Things to know:
+
+- **Tool names and model names are sent as-is** when they look like identifiers. Do not put secrets in tool names.
+- **The feature label defaults to `module.function`** of the code that made the call. Set it yourself with `zexl.feature()` if your function names are sensitive.
+- **Lengths are sent.** Character and token counts reveal how long a prompt was, not what it said.
+
+### How the hashes work
+
+The part of your key after the dot is a salt. It stays in your process and is never transmitted. Every hash is an HMAC-SHA256 keyed with that salt, cut to 128 bits. Without the salt a hash cannot be matched to text, including by Zexl, and hashes from different workspaces cannot be compared. If you lose the key, the salt cannot be recovered; a new salt starts a new hash history.
+
+### How this is tested
+
+`tests/test_leak.py` plants canary strings in every place content can appear (system prompt, messages, images, tool definitions, tool arguments, tool results, responses, streamed chunks, error bodies), runs each supported call style, and fails if a canary or the salt appears in any byte the SDK sends. It also plants a deliberate leak to confirm the check would catch one.
+
+## Behaviour you can rely on
+
+- **Your calls are never blocked or changed.** Capture runs around the provider call; delivery happens on a background thread. If Zexl's intake is down, records are dropped and your application carries on.
+- **Errors inside the SDK never reach your code.** They are logged once on the `zexl` logger at warning level.
+- **Exceptions from the provider pass through untouched.**
+- **Bounded memory.** At most 2,048 records wait for delivery; beyond that the SDK drops records.
+- **Delivery is tried, not guaranteed.** Records go out every 2 seconds or every 256 records. A send that times out, loses its connection, or gets a 429 or 5xx is tried once more after 1 second. If that also fails, the batch is dropped and the SDK waits before the next send, from 2 seconds up to 60 seconds while the outage lasts.
+- **No dependencies.** The SDK uses only the Python standard library.
+
+`zexl.status()` reports whether capture is on, which hooks are active, and how many records were sent or dropped.
+
+## Overhead
+
+Measured with `bench/overhead.py` on a laptop (Python 3.12, 14 Nov 2026). The provider is a
+mock inside the process, so these figures are the SDK's own work, not network time.
+
+| Call | Time added per call (median) |
+|---|---|
+| Chat or messages call, 1 KB prompt | 0.05 ms |
+| Async chat call, 1 KB prompt | 0.05 ms |
+| Streamed chat call, 200 chunks | 0.32 ms for the whole stream |
+| Agent step, 60 KB history and 10 tools | 0.23 ms |
+| Agent step, 1 MB history | 1.4 ms |
+
+Memory: a process that made 5,000 agent-step calls peaked 12 MB higher with the SDK on, and
+16 MB higher when the intake was down the whole time. The queue holds at most 2,048 records;
+beyond that the SDK drops records, so memory does not keep growing.
+
+Sending happens on a background thread and never delays your call.
+
+## What is recorded
+
+| Provider | Covered |
+|---|---|
+| OpenAI | `chat.completions.create`, `.parse`, `.stream`; `responses.create`, `.parse`; streaming; `with_raw_response`; sync and async |
+| Anthropic | `messages.create`, `.parse`, `.stream`; `beta.messages`; streaming; `with_raw_response`; sync and async |
+
+Tested with `openai` 1.68 to 3.50 and `anthropic` 0.50 to 2.8, on Python 3.10 and 3.13.
+
+Known limits:
+
+- **Streamed OpenAI chat completions report no token usage** unless you pass `stream_options={"include_usage": True}`. Without it Zexl estimates cost from character counts. Setting `ZEXL_OPENAI_STREAM_USAGE=1` adds the option for you; it makes OpenAI send one extra final chunk with an empty `choices` list, so check your stream-handling code first.
+- **`with_streaming_response` calls are recorded without response details**, because the SDK does not read the body ahead of you.
+- **Retries inside the provider SDK are invisible.** A call that succeeded on its third attempt is one record.
+- **Not yet covered:** the Bedrock, Vertex and Azure client variants are untested, and other providers and agent frameworks are not hooked.
+
+### Runs
+
+A run is one unit of agent work. Without any code from you, the SDK groups calls into a run when each request continues the previous response (the usual agent loop), or uses `previous_response_id`. If your application already has an OpenTelemetry trace active, the trace is the run.
+
+Automatic grouping does not work when your agent trims or summarises its message history, or for sub-agents with their own conversations: those appear as separate runs. Wrap the work in `zexl.run()` to group it.
+
+## Development
+
+```bash
+uv sync
+```
+
+```bash
+uv run ruff check . && uv run ruff format --check . && uv run mypy && uv run pytest
+```
+
+Measure what the SDK adds to a call (time per call, peak memory), against a mock provider:
+
+```bash
+uv run python bench/overhead.py
+```
+
+Test against several provider SDK versions (from the repository root):
+
+```bash
+scripts/sdk-matrix.sh
+```

zexl-0.1.0/pyproject.toml

@@ -0,0 +1,69 @@
+[project]
+name = "zexl"
+version = "0.1.0"
+description = "See how much of your AI spend did useful work, without sending a single prompt."
+readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+authors = [{ name = "Zexl" }]
+keywords = ["llm", "ai", "cost", "observability", "openai", "anthropic"]
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Typing :: Typed",
+]
+requires-python = ">=3.10"
+dependencies = []
+
+[project.urls]
+Homepage = "https://tryzexl.xyz"
+
+[dependency-groups]
+dev = [
+    "pytest>=8",
+    "pytest-asyncio>=0.24",
+    "ruff>=0.8",
+    "mypy>=1.13",
+    "openai>=1.40",
+    "anthropic>=0.40",
+    "httpx",
+    "opentelemetry-api",
+]
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/zexl"]
+
+[tool.hatch.build.targets.sdist]
+include = ["src", "README.md", "LICENSE"]
+
+[tool.ruff]
+line-length = 100
+target-version = "py310"
+
+[tool.ruff.lint]
+select = ["E", "F", "I", "B", "UP", "S"]
+
+[tool.ruff.lint.isort]
+known-first-party = ["zexl", "clients", "providers", "conftest"]
+
+[tool.ruff.lint.per-file-ignores]
+"tests/*" = ["S101", "S105", "S106", "S603", "E501", "E731"]
+"bench/*" = ["S101", "S105", "S603"]
+
+[tool.mypy]
+strict = true
+files = ["src"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+asyncio_mode = "auto"
+filterwarnings = ["ignore::DeprecationWarning"]