chatsee-anthropic
ChatSee connector for the Anthropic Messages API.
pip install chatsee-anthropic
from anthropic import Anthropic
from chatsee_anthropic import instrument_anthropic
client = Anthropic(api_key="...")
instrument_anthropic(client, agent_id="...", tenant_id="...")
That is the whole integration. Your agent code does not change —
client.messages.create(...) still returns exactly what it returned before.
chatsee-ai is installed for you as a dependency.
What it captures
Per turn: the user's question, the assistant's answer, the system prompt, every tool call with its arguments and result, and one model call per model call with the tokens Anthropic reported for it.
Three backends, one connector
Anthropic, AnthropicBedrock and AnthropicVertex (and the Async variants)
all expose the same Messages resource. The connector detects which one you
built and labels the provider anthropic, bedrock or vertex — it never
assumes. Streaming via messages.stream(...) is captured too.
The part worth knowing
messages.create fires once per loop step, not once per turn. A
tool-using turn calls it at least twice — once to ask for the tool, once to
answer — and each call reports its own usage.
So the connector accumulates model calls across the steps of a turn and emits
when the turn ends, which is the step whose stop_reason is not tool_use.
Capturing only the final response would silently drop the first step's tokens
and every tool-using turn would look cheaper than it was.
Guarantees
- Fails open. A failure inside capture is logged and swallowed. ChatSee can never break your agent.
- Idempotent. Instrumenting the same client twice is a no-op.
- Concurrency-safe. Turns are keyed per conversation, so one client serving several users at once does not mix them up.
All three are enforced by the contract suite, not just intended.
Tests
No network, no API key, no dev tenant — the Anthropic SDK is stubbed, ChatSee is not.
pip install -e python/connectors/_shared
pip install -e python/connectors/ai_sdk/anthropic
pytest python/connectors/ai_sdk/anthropic/tests -q
Metadata
Release files for chatsee-anthropic 0.1.0
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 |
|---|---|---|---|---|
| chatsee_anthropic-0.1.0.tar.gz | 9.2 kB | Without provenance | Details for chatsee_anthropic-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| chatsee_anthropic-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for chatsee_anthropic-0.1.0-py3-none-any.whl |
Total release size: 16.9 kB
Release files / chatsee_anthropic-0.1.0.tar.gz
| Download URL | chatsee_anthropic-0.1.0.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b48daeab35b3dd9d6fba287a314cf97bd253b5bd491174de1f19a658208d710d
|
|
BLAKE2b-256 checksum How to use checksums |
4ede50a3f0e444ee31b178d39685ab2f272e2e3b765dfef7c40714c4c16eb2b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.11
|
Release files / chatsee_anthropic-0.1.0-py3-none-any.whl
| Download URL | chatsee_anthropic-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b13b2de702ac6b4eb9cbe97580b49de728f841c63f8e42e993b0749a1531ca6b
|
|
BLAKE2b-256 checksum How to use checksums |
1b3a5d8d45ad62977869902baf2e1e1dfabeaad9e53c9d69d665a47fcc9a5373
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.11
|
Security for chatsee-anthropic 0.1.0
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.