Averth

Analyze a sanitized batch of agent run records and compute fully-loaded cost per accepted outcome, the expensive-tail share of spend, and a breakdown across the five cost layers (context compounding, external tool spend, token yield, heavy tail, model mix plus human review). ledger_json is a JSON array of run records; each record may include run_id, model_cost, tool_cost, retry_cost, human_cost, human_minutes, retries, input_tokens, output_tokens, waste_tokens, total_cost, success, outcome_inferred, outcome_unknown, reopened, business_value, model_name. An averth export_ledger object (with an 'attempts' array) is also accepted. A run with no recorded outcome is outcome-unknown: it counts as neither a success nor a failure, and cost per accepted outcome is never computed from it. Redaction warning: ledgers export caller free text verbatim, including case_id, tool names, and retry reasons, and that free text can contain customer data; redact sensitive values before sharing. The ledger is processed in memory only and is never stored.

analyze_run_batch

Explain the five cost layers used to compute fully-loaded agent economics: context compounding, external tool spend, token yield, heavy-tail outliers, and multi-model attribution with loaded human labor. Returns a static explainer; takes no input.

explain_cost_layers

Replay a hypothetical cost policy against a submitted run ledger, offline. Reports which completed runs crossed the proposed thresholds and how much historical spend is associated with those runs, split between historical spend on failed runs that would have been stopped and collateral (successful runs that would have been stopped). This is never projected savings: a live policy acts mid-run, not on completed runs. policy_json is a JSON object with optional keys: max_cost_per_attempt (stop runs costing more than this many dollars) and yield_floor (stop runs whose token yield falls below this 0-1 fraction). At least one must be set. This is a historical replay only: it enforces nothing, changes nothing, and the ledger is processed in memory and never stored.

simulate_policy