One card per vendor: what the vendor charges per, what its own published
rules say, and where every fact came from. This is the same
registry
file the CLI and the browser recount read — a parity test in CI keeps the three from
drifting. Registry version v0.5.0.
AdaS
rule card · registry v0.5.0
- Price
- not published
- Billing trigger
- an internal algorithm classifies the conversation as resolved
- Reopen handling
- no documented reopen deduction
- Silence bills
- yes — window 24h
- Closure timers
- email: 72h · social: 24h · web: 24h
- Source
- ada.cx pricing/terms returned 403; rule reported from public docs
operator feedback does not override the automatic classification
Re-run the recount yourself: in the browser or agentmeasure recount --vendor ada. Rules change; this card records the version it was read from.
Generic per-resolution vendorU
rule card · registry v0.5.0
- Price
- not published
- Billing trigger
- no published rule — only the AgentMeasure standard applies
- Reopen handling
- no documented reopen deduction
- Silence bills
- unknown
- Closure timers
- not published
- Source
- no vendor rules; only the AgentMeasure standard is applied
Re-run the recount yourself: in the browser or agentmeasure recount --vendor generic. Rules change; this card records the version it was read from.
HubSpot BreezeS
rule card · registry v0.5.0
- Price
- USD 0.5 per resolution
- Billing trigger
- assumes resolution after a lock window; a reopen after the lock starts a fresh billable window
- Reopen handling
- none after the lock window
- Silence bills
- yes — window 72h
- Closure timers
- email: 72h · messaging: 72h
- Source
- secondary; knowledge.hubspot.com is JS-only and could not be read
a reopen after the 72-hour lock starts a FRESH billable window instead of deducting the original, which is a double-billing risk rather than a protection
Re-run the recount yourself: in the browser or agentmeasure recount --vendor hubspot. Rules change; this card records the version it was read from.
Intercom FinP
rule card · registry v0.5.0
- Price
- USD 0.99 per resolution
- Billing trigger
- bills on confirmed or assumed resolutions (silence can bill)
- Reopen handling
- documented reopen deduction, including across billing periods
- Silence bills
- yes — window 24h
- Closure timers
- email: 72h · messaging: 24h
- Source
- fin.ai pricing & outcomes; Intercom help centre (Fin AI Agent outcomes)
- confirmed resolution rate and assumed resolution rate are separate published metrics, so a buyer can at least see the split
- resolution state is filterable and exposed via API v2.11+
Re-run the recount yourself: in the browser or agentmeasure recount --vendor intercom. Rules change; this card records the version it was read from.
Salesforce Agentforce Help AgentU
rule card · registry v0.5.0
- Price
- not published
- Billing trigger
- bills on autonomous completion (no published timer or reopen rule)
- Reopen handling
- no documented reopen deduction
- Silence bills
- unknown
- Closure timers
- not published
- Source
- press release only; no official metering document is published
- no timer, no reopen rule, and no clawback are published
- the broader Agentforce product is billed whether or not the issue was resolved
Re-run the recount yourself: in the browser or agentmeasure recount --vendor salesforce. Rules change; this card records the version it was read from.
Zendesk AI AgentsP
rule card · registry v0.5.0
- Price
- USD 2.0 per resolution
- Billing trigger
- only an affirmative model adjudication counts — silence alone is free
- Reopen handling
- no documented reopen deduction
- Silence bills
- no
- Closure timers
- email: 72h · messaging: 2h · voice: 0h
- Source
- Zendesk help centre: About the automated resolutions platform; About automated resolution tiers (edited 2026-08-25)
- criteria, thresholds and error rate behind the LLM adjudication are not published
- unused allowance does not roll over to the next billing period
deleting a ticket with Resolution type Automated does not undo the consumption of an automated resolution
Re-run the recount yourself: in the browser or agentmeasure recount --vendor zendesk. Rules change; this card records the version it was read from.