VERIFYGRID REGISTRY TOOL // VERIFY_PROVIDER_NPI
Healthcare 10-Digit NPI Registry & OIG LEIE Verification.
Verify Type 1 (Individual) and Type 2 (Organization) National Provider Identifiers against CMS NPPES and HHS OIG List of Excluded Individuals and Entities.
Live Edge Endpoint & Schema
- REST ENDPOINT
- GET /v1/verify/provider?npi=1245319599
- MCP TOOL
- verify_provider_npi
- CREDIT COST
- 2 CREDITS / CALL
- AUTHORITY FEED
- CMS NPPES API v2.1 + HHS OIG LEIE
- SAMPLE INPUT
- 1245319599
Deterministic JSON Response Fields
npientity_typeprovider_nametaxonomy_codetaxonomy_descpractice_stateoig_leie_excludedcms_status
Instant cURL & MCP Execution
# 1. Direct REST Verification
curl -s "https://www.verifygrid.io/v1/verify/provider?npi=1245319599" \
-H "Authorization: Bearer vg_test_sandbox"
# 2. Streamable HTTP Remote MCP Call
curl -s -X POST "https://www.verifygrid.io/mcp" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "verify_provider_npi",
"arguments": {}
}
}'
// FAQREGISTRY & INTEGRATION SPECIFICATIONS
Does VerifyGrid query the live CMS NPPES v2.1 API?
Yes. VerifyGrid checks D1 edge cache first and queries https://npiregistry.cms.hhs.gov/api/?version=2.1 on cache miss while scheduled cron jobs ingest delta updates every 6 hours.
Are HHS OIG LEIE exclusions included in the NPI response?
Yes. Each NPI lookup returns oig_leie_excluded so healthcare credentialing pipelines can block excluded providers in a single call.