The developer front door for the Verzi Health API. Every answer comes with a receipt: the verbatim CMS source, its version, and the date of service. Live for Medicare DME. Date-of-service LCD and policy article text, verbatim from CMS. Versions back to October 2015.
The API your team was about to build internally, plus the one thing nobody builds twice: a hash-pinned history of what the rules said on a date.
A signed answer covers one claim line as of its date of service: provider standing, coding edits, and the fee cell, each with a replayable receipt, plus the documentation rule where approved (E0601 and K0606 today). See how a signed answer works.
Archived versions of LCDs, articles, and coverage documents back to October 2015, where CMS kept them.
Every claim cites its source. /sources lists every dataset with license and refresh history. Every signed answer and every archive answer carries the source document, version, and sha256.
All data is provider-, facility-, or population-level, from public primary sources. Full disclosure statement.
Standard REST + an X-API-Key header. Or use the TypeScript SDK, or point an agent at the MCP server.
During the private beta, access to a signed answer is granted per account.
Use your work email: we email a code to confirm it, then show your key. Free email providers are not supported. No credit card.
The cited, as-of answer with a receipt you can replay.
Most healthcare data platforms keep their methodology proprietary. We publish ours.
Row counts, source counts, last pipeline run, last refresh status.
View liveEvery dataset we ingest, with source agency, license, refresh cadence, and last-loaded timestamp.
View catalogPer-source audit log. Every load attempt, success or failure, timing, row counts, error message.
View exampleEvery archived version of a policy document, with effective dates, hashes, and the version in force on a date.
Open the archiveFree tier, no credit card, and the first call is a public one.
Get your API key
