36 source authorities mapped·coverage as of 2026-06-05

The credibility is the sources. Not the logos.

Every verified claim is built to trace to a primary authority, and is designed to lock a receipt only when that source returns a match. Here is exactly what we check, how we check it, and where the path is still manual. We are pre-launch: no production verifications have run at scale yet.

AI operates the workflow. Source systems prove the facts. Humans make every regulated decision.

Source authorities mapped

Roles supported

Jurisdictions, all states plus DC

2,193

Coverage cells, 0 unsupported

The coverage map

43 roles × 51 jurisdictions = 2,193 cells.

Every cell has a defined verification path. Where a live API exists, we use it. Where it does not, we are honest that the path is manual primary source verification, performed and receipted the same way. These counts describe supported verification paths across a synthetic 43-role corpus, not completed verifications of real workers.

Hover or tap any cell to see its verification path.snapshot of /workforce/verification-coverage · 2026-06-10 · query it yourself

API path · 408 cells Manual PSV path · 1,785 cells 0 unsupported

The authorities

What we check, and how.

A representative view of the source layer. Connected means the integration is built, authenticated, and canary-tested against the authority. Manual means a defined primary-source path we perform by hand. Roadmap means access is in progress. We are pre-launch: no production worker verifications have run yet.

Source authorityMethodCoversStatus

NPDBNational Practitioner Data Bank API Malpractice, sanctions, adverse actions Connected

Nursys e-NotifyNCSBN API RN / LPN license status, 25 boards Connected

NPI / NPPESCMS registry API Provider identity, enumeration Connected

OIG LEIEOffice of Inspector General API Federal exclusions list Connected

SAM.govSystem for Award Management API Federal debarment, exclusions Connected

DEA registrationcontrolled-substance authority Manual PSV Prescriptive authority status Manual

State nursing boards25 boards integrated API License status by jurisdiction Connected

State boards, remainingnon-API jurisdictions Manual PSV License status where no API exists Manual

Payer enrollment adapters5 payers API · partial Clear-to-bill enrollment status In progress

ABMSAmerican Board of Medical Specialties Roadmap Board certification, physician Access in progress · Q3 2026

AMAAmerican Medical Association Roadmap Physician profile, education Access in progress · Q3 2026

FSMBFederation of State Medical Boards Roadmap Physician board actions, history Access in progress · Q3 2026

A representative selection of the 36 source authorities. The receipt examples shown are illustrative; coverage counts are current as of 2026-06-05. DEA is shown on the manual path conservatively pending production attestation flow.

Nurse-license API coverage runs through Nursys e-Notify (multi-state) plus 25 direct board APIs; remaining jurisdictions fall to the manual primary-source path.

See all 36 source authorities

The 36 mapped authorities: NPDB; Nursys e-Notify (NCSBN); NPI / NPPES (CMS); OIG LEIE; SAM.gov; DEA registration; the 50 state boards of nursing plus DC (25 with a live board API, the remainder on the manual primary-source path); the 5 payer enrollment adapters (Aetna, BCBS, Cigna, Humana, UnitedHealthcare); ABMS; AMA; and FSMB. State nursing boards and payer adapters are counted as their constituent authorities, which is how the total reaches 36. Query the live count at /workforce/verification-coverage.

Honest by design

We never dress manual work up as an API.

API verification

Where an API exists, a query returns a receipt locked to the source response in seconds. These integrations are built and canary-tested; verification is pre-launch. This is most of the coverage map.

Manual primary source

Where no API exists, a defined manual path verifies against the same primary source. It takes longer, and the receipt records that it was performed by hand. Same proof, stated plainly.

Roadmap ABMS, AMA, and FSMB are on the roadmap. Access is in progress, targeted for Q3 2026. Until those integrations are live, physician board data follows the manual primary-source path, and we label it as such.