cost_drift is one of Tessary's built-in classifiers: a tripwire that watches each call site's spend against its own past. It tracks dollars per turn, with token counts attached as evidence.
It catches the quiet ways an agent gets more expensive: a prompt that grew, retries that multiplied, caching that stopped working. Comparisons run against the call site's own history, both its recent normal and a reference pinned at the last deploy, so sudden jumps and slow creep both register. A drop in cost shows up as clearly as a rise. Findings go to triage, where the ones ruled real issues open cases.
5 questions
Answered, plainly.
Two ways to run Tessary.
Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.
Tessary Cloud
We host it for you. Send your first trace with nothing to deploy and no model key.
- traces
- 10,000 per calendar month
- stored trace data
- 1 GB
- retention
- 30 days
- model credit
- $10, one-time, for triage and root-cause analysis
- credit card
- not required
Self-hosted Tessary
Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.
Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md
docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y