DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to re-count an AI support bill against the vendor rule with Agent Measure

Run the free CLI on a billing export to see overcharge and undercharge findings, unsettled rows and dollar variance.

  • Top pick
  • Money
  • Intermediate
  • 30 minutes
  • From the README
  • Any agent

Credentials. The export contains customer conversation records, so remove any personal data your policy does not allow in a local tool before running the command.

Who it is forA support operations lead or finance reviewer who received a per-resolution AI support invoice from Intercom, Zendesk, HubSpot, Salesforce, Ada or a similar vendor and wants to check it.

The problemThe invoice counts AI resolutions, but the team cannot tell whether each charge follows the vendor's stated billing rule or whether some rows lack the evidence to decide.

The outcomeA list of findings in both directions, rows marked cannot settle, the vendor rule with its public source, and a dollar net variance that can inform a vendor review.

What you need first

  • Python 3.9 or newer and pip
  • A terminal on macOS, Linux or Windows
  • A vendor billing export as CSV for the recount use case, or local Codex or Claude Code session logs for the log use cases
  • Permission to read the session logs or export files you point the tool at

Steps

  1. Run pip install agentmeasure to install the CLI from PyPI.
  2. Save your reviewed billing export as export.csv using the canonical columns the README shows: conversation_id, human_agent_participated, issue_addressed, customer_recontacted_within_window and vendor_billed.
  3. Run agentmeasure recount --list-vendors to confirm which vendor rule sets ship and their confidence grades.
  4. Run agentmeasure recount --export export.csv --vendor zendesk, replacing zendesk with your vendor's rule if it differs.
  5. Read the findings in both directions and the rows in cannot settle. Treat the dollar net variance as a rule-priced finding, not recovered money.

Prompt for your agent

Using the AgentMeasure repo, run `agentmeasure recount --export <export.csv> --vendor <vendor>` on the file at <export.csv> and report the overcharge, undercharge, net variance and count of cannot settle rows. Verify that rows without enough evidence are excluded from the claim rather than zeroed.

Caveat. A recount is arithmetic under a published rule, not a verdict on the vendor, and a finding is not an accepted claim or a refund.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page