MedBillAnalyzer

Reviewed 5h ago. Tool definitions changed on Oct 11, 2026.

• tools: 7 tools scanned
• metadata: scanned

• mediumReviewTool definitions changed after an earlier review

  A server that changes its tool descriptions after being approved ("rug pull") can slip new instructions to agents. Re-check what changed before trusting it.

  changed 2026-10-11

Tools (7)

• check_medical_bill

  Compare a medical bill against the Explanation of Benefits the patient’s insurer issued for the same care, and report where the two disagree. Use when someone shares a medical bill, hospital statement, doctor bill, lab bill or EOB and asks whether it is correct, what they actually owe, or how to dispute it. The bill is required; the EOB is strongly recommended and is what makes most of the checks possible. If you can see the documents but cannot attach their bytes, transcribe them into `bill` and `eobs` exactly as printed. Free: returns a summary and the title of every finding, but not the detail behind them.

• get_case

  Retrieve a case by id. Returns the same free summary, plus every finding in detail once the case has been unlocked.

• unlock_case

  Pay to unlock the full findings, the dispute letter and the phone script. With a `shared_payment_token` (a Stripe Shared Payment Token granted to the `stripe_profile` in the case summary's `purchase`), it charges $10.00 for this bill and unlocks the case in the same call. Without one, it returns a checkout URL and charges nothing itself. A case with no findings is refused: there is nothing to buy, and the user pays nothing when nothing is found. So is a case with nothing to act on yet (`nothing_to_act_on`), such as a bill sent without its Explanation of Benefits whose only finding is that the EOB is missing.

• get_case_outputs

  Get the dispute letter and the phone script for an unlocked case. The letter is a template the patient sends in their own name.

• delete_case

  Delete everything held about a case, immediately and permanently. The record is removed, not flagged, and it cannot be recovered afterwards — not by us either. This is the promise the privacy policy makes, and it needs no account. It does need the delete token issued when the case was created: reading a case and destroying it are deliberately different capabilities.

• report_outcome

  Record what happened after the patient sent the dispute letter: corrected, reduced, refused, ignored, still waiting, or not sent. Free. Every answer counts equally, and it is kept only as an aggregate count — nothing about it is stored against the case. This product can tell that two documents disagreed; only these reports show whether saying so to a billing office changes anything.

• export_case

  Everything stored about a case, as JSON, in one response. This is the portable copy the privacy policy offers. It is deliberately the whole record rather than a summary, so that what is returned here can be compared against what the policy says is kept.