STEP 2
Make your first request
Check a DME code. This looks up E0601, a CPAP device, for Colorado on 2026-08-15. Put your key in VERZI_API_KEY and run it.
What a free key returns. signed_receipt.included is false. The signed receipt comes with a paid plan or a design partner plan. The object below is a real free-key response for this call.
{
"hcpcs": "E0601",
"date_of_service": "2026-08-15",
"state": "CO",
"descriptor": "Continuous positive airway pressure (cpap) device",
"public_level_ii": true,
"license_note": null,
"coverage": {
"status": "lcd_listed",
"summary": "CMS lists E0601 on 1 LCD in the Medicare Coverage Database code table."
},
"governing": {
"lcds": [
{
"id": "L33718",
"doc_id": "lcd:33718",
"title": "Positive Airway Pressure (PAP) Devices for the Treatment of Obstructive Sleep Apnea",
"version_listed": 52,
"in_force": "Version 52 is the one in force on 2026-08-15.",
"in_force_status": "ok",
"in_force_reason": null,
"cms_url": "https://www.cms.gov/medicare-coverage-database/view/lcd.aspx?lcdid=33718",
"cms_description": "CONTINUOUS POSITIVE AIRWAY PRESSURE (CPAP) DEVICE",
"articles": [
{
"id": "A52467",
"title": "Positive Airway Pressure (PAP) Devices for the Treatment of Obstructive Sleep Apnea - Policy Article",
"cms_url": "https://www.cms.gov/medicare-coverage-database/view/article.aspx?articleid=52467"
},
{
"id": "A55426",
"title": "Standard Documentation Requirements for All Claims Submitted to DME MACs",
"cms_url": "https://www.cms.gov/medicare-coverage-database/view/article.aspx?articleid=55426"
},
{
"id": "A58824",
"title": "Response to Comments: Positive Airway Pressure (PAP) Devices for the Treatment of Obstructive Sleep Apnea – DL33718",
"cms_url": "https://www.cms.gov/medicare-coverage-database/view/article.aspx?articleid=58824"
}
]
}
],
"ncds": [],
"ncd_note": "Verzi does not hold a CMS code-to-NCD crosswalk, so this lookup does not name a National Coverage Determination. The governing local policy is the LCD CMS lists for the code."
},
"documentation_requirements": {
"status": "ok",
"reason": "approved_labels_not_in_force",
"served": 0,
"pending": 0,
"completeness": "unlabeled",
"kb_url": "https://kb.verzi.health/kb/free/E0601"
},
"prior_authorization": {
"status": "ok",
"reason": null,
"value": "not_listed",
"summary": "The list version in force on the date of service does not name this code.",
"scope": null,
"list_title": "REQUIRED PRIOR AUTHORIZATION LIST"
},
"citation": {
"publisher": "Centers for Medicare & Medicaid Services",
"source": "Medicare Coverage Database, LCD code table",
"code": "E0601",
"document": "L33718",
"title": "Positive Airway Pressure (PAP) Devices for the Treatment of Obstructive Sleep Apnea",
"archived_on": "2026-10-09",
"file_sha256": "55e6fdfaaba5dba5d20be094037c0aefaea4cf0fb3d914bf18827789d1ddf40a",
"cms_url": "https://www.cms.gov/medicare-coverage-database/view/lcd.aspx?lcdid=33718"
},
"signed_receipt": {
"included": false,
"signup_url": "/signup",
"note": "The signed receipt for this code needs a paid plan: the signature, the archived file, and the span of each requirement. A free key opens the source archive and the catalog."
},
"canonical": "https://api.verzi.health/check/E0601?state=CO&dos=2026-08-15",
"meta": {
"as_of": "2026-08-15"
}
}
Where does the API key go? In the x-api-key header. Never in the URL or a query parameter. Request logs and referrers would leak it.
STEP 4
Handle rate limits + errors
Every response includes rate-limit headers. When you hit your daily cap, you get a 429 with a reset timestamp. No surprise overage charges — we never bill you for usage you didn't sign up for.
$ curl -i -H "X-API-Key: $KEY" https://api.verzi.health/hospitals
HTTP/2 200
X-RateLimit-Limit: 1000
X-RateLimit-Remaining: 97
Content-Type: application/json
...
Rate limit hit? Response is
429 Too Many Requests with the reset time in the body. For higher limits, contact us at
adrian@verzi.io, or wait until
00:00 UTC for the counter to reset.
