Developers · 41,000+ rules · 51 states · CMS-0057-F + CMS-0062-P
One corpus, six surfaces.
Pick the tab that fits your stack — same rules, same response shape, same source URLs everywhere.
How the API works — four steps
1
Auth
Set header: x-api-key: <YOUR_UUID_KEY>
2
Request
GET /v1/pauth-lookup?state=CA&program=medicaid_ffs&drug=glp_1_agonists
3
Response
200 OK · JSON verdict + confidence + source_url + next_steps
4
Reach
Six surfaces — REST, SDK, FHIR, MCP, Embed, Salesforce — same corpus, same shape
REST
REST API
Pure HTTPS · OpenAPI 3.1 · any language
The lowest-friction path. One header, one GET, one JSON body back. The same corpus that powers every other surface on this page — 41,000+ verified drug, procedure, and service rules across 51 states and 6 programs, scoped to CMS-0057-F (final, in force) and CMS-0062-P (proposed). Source URLs and last_verifiedtimestamps in every response. And /v1/action-plangoes past “is it covered?” to “what do I do?” — ranked actions with filing deadlines, the appeal ladder, and the real member-services numbers to call.
Endpoints
/v1/pauth-lookup (coverage verdict) · /v1/action-plan (ranked next steps + deadlines + who-to-call)
Auth
x-api-key: <UUID v4>
Latency
<300ms p95 from US-east edge
Rate limit
10,000/hr · 429 + Retry-After
CORS
Access-Control-Allow-Origin: *
Spec
OpenAPI 3.1 · Postman / Insomnia importable
loading…