Last updated October 13, 2026

Terms of use

These terms cover the verzi.health website and the Verzi Health API, SDK, and MCP server (the “service”), operated by Verzi Health. By using the site or calling the API, you agree to them. If you are using the service for a company, you are agreeing for that company.

Public Medicare reference data

The service serves public Medicare reference data: the published rule, edit, fee, and standing as of a date of service, with the version and a hash you can replay. It is live for Medicare DME. The rest of Medicare and Medicaid are coming soon, then commercial plans. The source archive and as-of resolution are public. The signed-answer endpoint (/v1/rules/warrant) requires an API key.

CMS and other publishers remain the authors of the underlying rules and files. Verzi signs the record of what was published and which version was in force. Verzi does not replace the publisher.

Not a guarantee of payment

A receipt is not a guarantee of payment or medical necessity, and it is not medical, legal, or billing advice. You are responsible for the claims you submit and the decisions you make with the record.

No HIPAA BAA

Verzi Health does not offer a HIPAA Business Associate Agreement. The service is not a store for protected health information. Do not submit PHI, patient identifiers, or identifiable claim payloads to the website, the contact form, or the API.

Accounts and keys

You can request an API key at docs.verzi.health/signup. Keys are for the account that requested them. Do not share a key, probe for other customers' data, or use the service to disrupt it. We may suspend a key that is abused or that breaks these terms.

Version listings, effective dates, hashes, and as-of resolution are public. CPT descriptors and original source bytes are gated to keyed, terms-accepted accounts. Those gated materials stay subject to the publisher's terms as well as these.

Acceptable use

Do not misuse the service: no attempts to break access controls, no overload that is meant to knock the API over, and no use of the output to misrepresent what a Medicare rule said on a date. Caching a response you are entitled to, for your own product, is fine.

The site

The marketing pages may show an example claim with real document names and a real fee next to other figures marked Example. The live archive, not the illustration, is what was in force. The contact form is described in the privacy policy.

Changes and the whole agreement

We may update these terms by posting a new version on this page with a new “Last updated” date. Continued use after that date is acceptance of the update. If a separate written agreement covers your account, that agreement controls where it conflicts with this page.

Questions go through the contact form.