Federal registries are maintained independently and routinely contradict each other. The clearest example: a provider EXCLUDED on the HHS-OIG LEIE whose NPI is still ACTIVE in the CMS NPPES registry — same NPI, two agencies, opposite status. We surface these cross-agency disagreements so your compliance, credentialing, or procurement team can verify before they pay, credential, or onboard. API + MCP + x402
Results appear here…
Primary check matches on the same NPI across LEIE and NPPES — confidence 1.0. No name-collision noise. A false match is worse than nothing.
You get both disagreeing records, each agency, the dates, the shared identifier, the match-confidence, and exactly what to verify.
A rolling feed of newly-detected high-confidence disagreements, rebuilt daily against the live registries.
MCP tool screen_disagreements — your agent verifies a counterparty mid-workflow. Pay-per-call via x402 (keyless USDC on Base).
GET /api/screen?npi=1003005315 # exact-id cross-agency disagreement check
GET /api/screen?name=ACME%20MEDICAL&state=NY
POST /api/screen {name?, npi?, uei?, state?}
GET /api/feed?limit=25 # feed of newly-detected disagreements
GET /api/feed/<npi> # one disagreement record
POST /mcp # MCP (screen_disagreements, list_disagreements)
Known disagreements: 500 · feed built 2026-08-20T07:26:40.930Z · docs & pricing · freshness · live feed
Activate (no account gate): email zivcomputerscience@gmail.com with your tier — PayPal invoice or wire/PO for Enterprise. Crypto: send + email the tx hash. USDT (TRC20) TNvb5tyrzWZW9iNUwQ6TTiY87MGLs1Cgsi · USDC (Base) 0x38134a7F97636E26365Fb17405566595B917a341