Find the warranty labour you were short-paid
A manufacturer pays warranty labour against its own published schedule — allowed hours per repair code, a multiple-repair increment, a travel rule, per-claim fee caps — and the remittance arrives as an amount, not a reconciliation. ClaimProof re-derives that schedule against what was actually paid, per line, with the rule and page cited. A repair code outside the version-stamped table is reported unstated and blocks the line — never zero.
The schematic's figures are the worked sample; the report computes yours from the claim and remittance you supply — the schedule's real allowances come from the vendored True Manufacturing form.
The declared fields below are the worked sample (two refrigeration repairs, an over-cap nitrogen fee, short-paid labour). Press Audit the claim to re-derive the vendored True schedule against the remittance in your browser — no model, no upload. The upload path reads the two documents as declared fields and answers with an explicit unconfigured error until the deploy carries the extraction key.
Watch the launch video
24s · nothing estimated · no signupClaimProof — find the warranty labour you were short-paid Watch on YouTube
Four stages, one deterministic chain
- Vendored scheduleThe allowed hours per repair code, the multiple-repair increment, the 30-mile travel rule and the per-claim fee caps come from the manufacturer's own published form — version-stamped, with the page each rule came from. A rule that cannot be cited is not vendored.
- Multiple-repair ruleMore than one repair in a call is paid at the highest-allowance line in full, plus the schedule's increment for each additional component — not the sum of each part's own full rate.
- Fee capsNitrogen, materials and reclaim fees are each capped by the schedule's own maximum. A fee over its cap is reported at the cap with the excess named, never silently dropped.
- Per-line varianceEvery line (labour, parts, fees, travel) is compared against the remittance, classified underpaid / correctly-paid / overpaid / unverifiable, and the sum of the line variances equals the batch variance — enforced in the engine.
The schedule publishes no fixed hourly labour rate — True reserves the right to pay no more than the average commercial rate in the territory — so labour is priced at the claim's own declared rate, and the parts line is compared as-filed (reimbursed at the OEM's distributor-cost basis, which the shop cannot re-derive).
Agent Surface & WebMCP Integration
How an agent invokes the warranty-remittance audit. The extraction layer reads declared fields; the audit itself is this deterministic engine.
// 1. In any browser with WebMCP support (auto-registered on page load):const audit = await navigator.modelContext.executeTool("audit_warranty_remittance", { schedule: "truemfg@2022-06", claim: claimDeclaredJsonOrText, remittance: remittanceDeclaredJsonOrText}); console.log("Verdict:", audit.report.verdict);console.log("Blocked lines:", audit.report.blockedLineCount);console.log("Stale schedule:", audit.report.staleSchedule);JSON Schema Parameters Contract
scheduleRequiredThe vendored schedule slug (e.g. truemfg@2022-06). An unknown slug is an explicit 400, never a default.
claimRequiredThe filed claim as declared-fields JSON (money in integer cents, time in tenths of an hour) or the claim document text for the extraction path. Every field carries value + provenance.
remittanceRequiredThe payment as declared-fields JSON or the remittance document text. The paid amounts are the evidence under audit — they are never derived from hours × rate.
Pricing
Use it free in the browser. Pay only for exports, the suite, or agent calls.
Free
$9.00 one-off
$29.00/month
| Agent tool | Metered rate |
|---|---|
audit_warranty_remittance | $1.50 per successful call |
Agent calls are metered per successful call and billed monthly to your Stripe customer. Billing shows your usage, history and spend cap.
Manage Billing & API Keys (/billing) →Agent surface: audit_warranty_remittance is registered as a WebMCP tool and advertised in /.well-known/mcp.json at $1.50 per successful call. The extraction layer it needs must be configured in the deploy environment first — until then the tool answers with an explicit unconfigured error naming the missing variable, never an estimated claim.