What we're building next

One JSON request returns the computed amount, the payability decision, and citations down to the CMS file row behind every input — so when a payer disputes a number, you can show exactly where it came from and which release answered.

• Historical lookups by year and quarter — ask for Q2 2024, get Q2 2024
• Locality by MAC code or plain ZIP, through the versioned crosswalk
• Gross or sequestration-net with one flag, never baked in
• payable=false always carries a machine-readable reason

The lookup answers "what does this code pay." The next question is harder: how did the fifty codes your practice lives on move this quarter, which localities disagree, and what needs a re-check before the next release lands.

• Cross-quarter rate deltas for a saved code set
• Locality comparison for negotiation and budgeting
• Bulk export in the shape your team already works in

Most practices know their payer contracts as "some percent of Medicare" and cannot say which percent, for which codes. Store your multipliers once, and every rate on the site becomes your rate — with underpayments flagged against what you were actually paid.

• Per-payer multipliers applied across every code page
• Upload a remittance, get expected-vs-paid per line
• Payer benchmark data from published MRF files

CMS reshuffles the fee schedule four times a year, and most people find out when payments change. Rate-change alerts already work; the ambition is alerting on the things that are harder to notice — a status flip, a new NCCI edit, an OPPS cap that started applying.

• Quarterly digests, or watch a single code
• Status and payability changes, not just dollar moves
• Specialty-scoped so you only hear about your codes