
clawmetry
UNCLAIMEDTRACING AND MONITORINGCOST AND USAGE TRACKING
clawmetry — See your agent think. Zero-config observability & governance for 30 AI agent runtimes: Claude Code, OpenAI Codex, Hermes, OpenClaw & 26 more. Live token costs, sessions, tool calls, crons. Listed under Tracing and monitoring in the Observability / Evals layer. 7 of 9 comparison attributes are recorded, each with the page it was read from.
Observe AI agent activity, understand spend, and govern supported actions with ClawMetry. Local by default. Start with one install.
4 OF 4 SIGNALS HELD
What it runs on, and what runs on it
0 cited edgesComputed from the stack graph, both directions. Every cited edge links the page it was read from; a vendor-added one links the vendor’s own source — this is the reason to be here rather than on the vendor’s own site.
No edges on record for clawmetry.
Nothing in the directory documents depending on it, and its own docs do not name what it runs on. An edge is only stored when a source states it.
Submit a documented integration →From clawmetry? No claim is needed for this: a link to your docs that names what clawmetry runs on is enough.
Open-source signals
A HOLLOW RING IS UNMEASURED, NOT ZERO · WE DO NOT SUBSTITUTE A PARENT COMPANY’S REPOSITORY FOR A PRODUCT THAT HAS NONE
Price
We hold no price for this product.
This is open-source software: you can run it yourself and the licence costs nothing. If the project also sells a hosted service, we do not yet hold the page it prices it on. If that changes — or if you publish /.well-known/pricing.json — it appears here with a capture date.
How we read prices →What its categories ask
7 answered · 2 unanswered9 questions declared by Tracing and monitoring and Cost and usage tracking. Most rows across the directory read like these.
“Put a limit on routed spend Use budget alerts for visibility. Route compatible model traffic through the optional proxy to enforce limits before another call.”2026-10-20
“Improve the economics Token and cost attribution, cache analysis, context usage, model routing advice and run comparisons. Cost optimization”2026-10-20
“Measured on the machine this page was written on: 102 sessions in 20 hours on 26 August 2026.”2026-10-20
“33 runtimes with shipped adapters. Coverage differs per runtime. The picker above says how, for yours.”2026-10-06
“MCP, OpenTelemetry, custom ingest, alert destinations and Enterprise SIEM export.”2026-10-13
A ROW WITH NO ANSWER IS NOT A ROW WITH A “NO” · A VENDOR MAY ANSWER A BLANK ONE, MARKED VENDOR CLAIMED WITH ITS SOURCE · A DOCUMENTED VALUE IS DISPUTED, NOT OVERWRITTEN, AND STAYS VISIBLE WHILE WE RE-READ THE SOURCE
Practitioner reviews
Nobody has written one yet.
A review here is structured, not a star: hardware, scale band, what broke in production, and whether you would choose it again.
NO PERCENTAGE IS SHOWN UNDER FIVE REVIEWS · NO STAR RATINGS, EVER
Also in this category
32 products in Tracing and monitoring. Comparison defaults to within the category — pairing this with a GPU cloud would produce a page that means nothing.
USED BY = LISTED PRODUCTS DEPENDING ON IT, IN THIS DIRECTORY
Frequently asked
Is clawmetry open source?
Does clawmetry offer budget limits?
Does clawmetry offer open source?
What does a blank mean on the clawmetry page?
Where do the clawmetry figures come from?
Can clawmetry change what this page says?
Something here is wrong — how do I fix it?
Is this listing run by clawmetry?
Cite this page
A model that quotes us should quote us correctly. The reading and its date sit inside the citation rather than beside it, because a quotation carrying only a URL goes wrong the week the URL changes.
infratoapp, “clawmetry — Tracing and monitoring”, read 20 October 2026. Budget limits: Yes as published at clawmetry.com. https://www.infratoapp.com/products/clawmetry
What clawmetry can and cannot change here
Claiming the organisation lets its admins and editors change the tagline, description, logo, docs link and deployment model of every product that org owns — live, labelled as theirs, and logged. Answers to blank questions and dependencies go live too, marked as the owner’s and sourced; a documented answer cannot be overwritten. Everything else on this page is a stated fact with a dispute route: price, licence and OSS figures. Those columns are ungranted at the database level, so they are not a feature we withheld — they are a write that cannot happen. Name, category, website, pricing page and package names can be changed by the owner only through our review. A dispute never deletes a value; it marks it and publishes the correction.