AgentMeasure

Check AI usage records. Re-count supported support-billing exports with evidence.

AgentMeasure checks Codex / Claude Code logs and applies published billing rules to supported AI support exports. Local CLI commands do not upload data. A PDF or invoice total alone is insufficient: recount needs reviewed event fields, and price-based differences are not verified refunds.

Your task	Start here
Explain a local duplicate, retry or failure	agentmeasure demo, then agentmeasure check; optional $10 interpretation
Check event accounting against one supported ruleset	Free input fit check, then bounded $20 Metering QA
Review a support-billing period	Free recount below; separate buyer feasibility review, not included in $10/$20

Website · 中文 · Healthcheck guide · Release notes

Re-count a bill in 60 seconds

Save this five-line sample as export.csv (synthetic data, real command):

conversation_id,human_agent_participated,issue_addressed,customer_recontacted_within_window,vendor_billed
c-001,N,Y,N,Y
c-002,N,Y,N,Y
c-003,N,Y,N,Y
c-004,Y,Y,N,Y
c-005,N,Y,Y,Y

pip install agentmeasure
agentmeasure recount --export export.csv --vendor zendesk

The output prints the vendor's rule with its public source, findings in both directions, then the dollars:

Dollars (at USD 2.0 per resolution)
overcharge identified       2.00
undercharge (vendor favour) 0.00
net variance                2.00

No CSV at hand? agentmeasure recount --sample runs the same bundled synthetic export in CLI 0.8.0. In this synthetic example, four rows remain unsettled; $8 is not a verified billable total. The $2 is a rule-priced finding, not recovered money.

Three reproducible showcase cases (overcharge with refused guesses, findings in both directions, the contract lane) live in examples/showcase with frozen expected outputs that CI compares on every change.

Repeat a billing review

For local-only handling, run the CLI on each new period's export. The optional GitHub Actions workflow requires a separate private repository and uploads data and reports to GitHub. Public forks are not private storage. Each period needs a fresh, reviewed export; no vendor data is fetched automatically.

Six vendor rule sets ship today — Intercom Fin, Zendesk AI Agents, HubSpot Breeze, Salesforce Agentforce, Ada and a generic per-resolution baseline — each citing its source and confidence grade (agentmeasure recount --list-vendors). When a recount disagrees with the invoice: agentmeasure prepare maps a native Intercom or Zendesk export onto the canonical columns, agentmeasure dispute builds the Dispute & Recovery Pack, and agentmeasure recovery records what the vendor actually conceded, counted separately from the claim.

A recount is arithmetic, not a verdict: rows without enough evidence land in cannot settle and are removed from the claim, never zeroed. "No finding" is a valid outcome. Vendor recounting is a free CLI capability, not one of the two paid services below.

Start with your own machine (free)

agentmeasure check inspects your local Codex / Claude Code sessions for duplicate records, retry amplification and token anomalies — the same evidence discipline pointed at your own logs. agentmeasure demo runs a bundled synthetic session with no account and no upload. Missing evidence stays unknown; a retry is not automatically a second logical operation.

Python 3.9+. CLI 0.8.0 on PyPI; Provider SDK 0.2.0 on npm, verified 2026-10-15. These packages have separate version numbers. On macOS/Linux use python3 -m pip if needed; on Windows use py -m pip. For permission or “externally managed” errors, use the virtual-environment instructions. With both runtimes present, auto-discovery prefers Codex; use agentmeasure check --runtime claude for Claude Code. No logs in the default seven-day window? Try --all or an explicit --dir and --runtime. A missing input is not a passing check. More recovery steps.

Compare Claude response evidence across files

agentmeasure response-audit first-session.jsonl fork-session.jsonl --json responses.json

This read-only command groups supplied response IDs and shows repeated usage snapshots, conflicts and missing fields. It does not rewrite logs, choose a winning snapshot or compute a session/invoice total. See the response-audit guide.

Get help with one question

Option	Price	What you get
Run the open-source tools	Free	Local Healthcheck, conformance checks, SDK and published rules
Healthcheck Diagnosis	$10	One anomaly on one machine: interpretation of your sanitized summary, evidence limits and next checks
Metering QA	$20	One event sample, one ruleset and one metering question: supported checks, findings and a rerun command

See scope, input requirements and apply by email. No subscription or sales call. First response within 24 hours. Delivery within 24 hours after payment, fit approval and complete input; queue changes are agreed before payment. A confirmation reserves a place; it does not start paid work. Card checkout is being set up; applications and price acceptance are separate from payment.

$10: counts alone support interpretation and general triage. Specific troubleshooting needs an optional manually redacted error excerpt; a root cause is not guaranteed. $20: fit is checked free before payment. Core FMT-002 checks operation/attempt accounting and sample cost conservation; it does not verify token/cache semantics, vendor invoices or pricing accuracy.

To prepare a summary locally:

agentmeasure check --json report.json
agentmeasure share report.json --out summary.json
agentmeasure validate summary.json

--out writes immediately on your machine. Inspect the file before you choose to send it. Nothing is automatically uploaded. Refund terms and evidence limits are on the service page; “no finding” and “not enough evidence” are valid outcomes.

No local mail app? Download an application template or copy the email. Attachments are manual. Do not send the full report.json, HTML report or raw logs when only a summary is requested. Tool bugs can be reported free in Issues, with a redacted reproduction.

For tool maintainers and providers

Resource	Use it for
Conformance pack	Check fixtures and reported metrics; PASS / FAIL / UNPROVABLE
Provider SDK	Capture canonical observations from MCP tool handlers: npm install @agentmeasure/mcp
Core specification and AMS-1	Define measurement grains and the evidence needed for claims
Claims index	Inspect dated findings, reproductions and upstream responses
Lab	Existing experimental tooling; no hosted product commitment

The buyer tools above (recount, prepare, dispute, recovery) share one end-to-end walkthrough. They are free CLI capabilities, not one of the two current fixed-price services. Current development priorities are in the roadmap.

Evidence and limits

The September audit report documents the 110-tool review. Individual findings and subsequent corrections are linked in the claims index. Engineering evidence does not establish paid demand, customer savings or a right to a refund. Customer value and repeat purchase remain under validation.

511 Healthcheck unit tests passed on 2026-10-15. See CI for current results and v0.8.0 for the release scope. Example fixtures are not production customer data.

Open-source commitments

• MIT-licensed tools and public rules remain free. Paying does not change a verdict.
• Analysis runs locally. Sharing a sanitized sample is your explicit choice.
• No paid rankings or recommendation slots; no payment custody.

Contributing · Security · Governance · Agent instructions · Whitepaper

Task scope and validation priorities · Developer guide