Skip to content
FonteumThe Graph

By use case

Exclusion & monitoring (self-serve)Free roster screen — no accountExclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligence

By buyer

Compliance & riskDevelopers & AI teams

By industry

HealthcareProviders & facilitiesFederal contractingSAM · USASpending · FAPIIS

The capability layer

APIREST + bulk accessMCP serverCallable by AI agentsFHIR R4 APIBulk exportAttestation & audit packReconciliationSource-vs-source diffsEntity graphSnapshotsPoint-in-time, bitemporal

The differentiator

Coverage & sourcesThe catalogFreshnessMethodologyCare CompareFacility qualityBrowse all datasets →
Research

The dev on-ramp

DocsAPI referenceMCP — connect your agentOne-paste installFHIR sandboxLive API surfaceQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inFree roster screen →Get a signed certificate →

Solutions

Exclusion & monitoring (self-serve)Exclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligenceCompliance & riskDevelopers & AI teamsHealthcareFederal contracting

Platform

APIMCP serverFHIR R4 APIBulk exportAttestation & audit packReconciliationEntity graphSnapshots

Data

Coverage & sourcesFreshnessMethodologyCare CompareBrowse all datasets →
Research

Developers

DocsAPI referenceMCP — connect your agentFHIR sandboxQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inFree roster screen →Get a signed certificate →
Side-by-Side Comparison

NPPES (CMS NPI Registry) vs CMS PECOS: Side-by-Side Comparison

NPPES and CMS PECOS are both CMS-operated federal systems for healthcare provider identity, but they serve distinct regulatory purposes. NPPES issues and maintains National Provider Identifiers — the 10-digit identifiers used on all HIPAA-covered claims. PECOS is the Medicare enrollment system — it tracks which providers are actively enrolled to bill Medicare fee-for-service.

Dimension by dimension

NPPES (CMS NPI Registry) vs CMS PECOS, across 8 dimensions

DimensionNPPES (CMS NPI Registry)CMS PECOS
Data typeFederal provider identity — 10-digit NPI, taxonomy code, practice addressMedicare fee-for-service enrollment — active billing authorization by specialty and state
Coverage8 million+ active NPI records (individuals + organizations)~900,000 active Medicare FFS enrollment records
Refresh cadenceWeekly publish by CMS; Fonteum re-checks per practice on a 6-month cycleMonthly CMS publish; Fonteum ingests the monthly file
License / CostU.S. government public-domain works (17 U.S.C. § 105) — free to use and redistribute with attributionU.S. government public-domain works — free to use and redistribute with attribution
API accessPublic REST API at npiregistry.cms.hhs.gov/api — no key required for basic lookupsCSV bulk download via data.cms.gov; no dedicated REST API
Source provenanceEvery field carries source + snapshot date + limitation; raw federal record is the direct upstreamSource row → snapshot → SHA-256 digest chain; per-field date on every rendered value
Primary use caseCanonical provider identity backbone — NPI lookup, taxonomy matching, cross-source joinsMedicare enrollment status checks, billing-authority signal on provider profiles
PricingFree (federal public domain)Free (federal public domain)

Cells marked “—” indicate values not publicly documented by the respective platform. No data has been estimated or fabricated.

Honest fit

Which platform fits your team

When to use NPPES (CMS NPI Registry)

Use NPPES as the identity backbone — any application that needs to look up a provider by NPI, resolve taxonomy, or join across multiple federal datasets starts with NPPES. Every CMS cross-source join flows through the NPI key.

NPPES (CMS NPI Registry) source detail →

When to use CMS PECOS

Use PECOS when the specific question is Medicare enrollment status — whether a provider is actively enrolled and authorized to bill Medicare FFS, and in which specialty and state. PECOS answers the billing-authorization question; NPPES answers the identity question.

CMS PECOS source detail →

FAQ

Common questions

Do all providers in NPPES appear in PECOS?
No. NPPES covers all healthcare providers who have enumerated an NPI — over 8 million records — including many who do not bill Medicare. PECOS covers only providers enrolled in Medicare fee-for-service, a smaller subset (~900,000 active enrollments). A provider can have an NPI (in NPPES) but not bill Medicare (absent from PECOS).
Which comes first — NPI or Medicare enrollment?
NPI enumeration (NPPES) comes first. Providers must obtain an NPI before applying for Medicare enrollment in PECOS. NPI is the primary identifier; PECOS records cross-reference NPI as the provider identity link.
Can I use NPPES data to determine if a provider is licensed?
NPPES records are administrative, not licensure records. An active NPI does not confirm current state licensure or board certification. For licensure, state medical board records are the authoritative source; for Medicare billing authorization specifically, PECOS is the relevant check.
How does Fonteum use both NPPES and PECOS?
Fonteum ingests NPPES for provider identity (NPI, taxonomy, address) and cross-resolves it against PECOS for Medicare enrollment status. A PECOS-enrolled provider gets a 'Medicare fee-for-service active' indicator on their profile, alongside the CMS provider type and enrollment state — each field with source attribution, last-checked date, and applicable limitation.

Last updated 2026-05-31. See all comparisons at /compare →

READY TO SHIP

Add federal-data citations to your agent in 60 seconds.

Drop our MCP server into Claude Desktop or call the API with pk_dx_sample. No signup. No credit card. Live demo key.

Add Fonteum to your agent →Request pilot access

Built on the authoritative federal record

The primary sources, named on every page.

These are the federal agencies whose public datasets Fonteum ingests and attributes — the issuing authorities, not customers or partners. Every figure on the site links back to one of them.

  • CMS
  • HHS-OIG
  • HRSA
  • FDA
  • NLM
  • NUCC
  • Census
  • BLS
  • BEA

See the full source registry, with license and refresh cadence for each →

Reproducible by design

Every figure traces to its federal source.

14-tuple provenance

Every rendered fact ties to a source URL, dataset ID, snapshot date, row key, and SHA-256 — the full chain-of-custody record.

Reproducible SQL

Each study ships the exact query behind its figures, run against the cited federal snapshot. Re-run it yourself.

Daily count checks

Published counts are checked against the upstream federal datasets on a daily cadence, with drift logged.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Two doors

Use the free API and open data

Query providers, facilities, sanctions, and quality scores — each field carrying its federal source. Self-serve, no call to start.

Explore the API →Browse the data catalog →

Talk to us

Managed pilots, enterprise terms, and audit-ready, signed attestation packages for compliance, risk, and research teams.

Talk to us →
Fonteum
Platform
Platform overviewAPIMCP serverFHIR R4 APIBulk exportAttestation & audit packReconciliationEntity graphSnapshots
Solutions
All solutionsExclusion & sanctions screeningCredentialing & enrichmentAudit evidenceProvider data for AI / RAGM&A & network diligenceCompliance & riskDevelopers & AI teams
Data & sources
Coverage & sourcesBrowse all datasetsState Medicaid exclusionsFreshnessMethodologyCare CompareSanctionsOwnershipStaffingDeficienciesSpecial Focus Facilities
Federal contracting
OverviewAwards during active exclusionFederal debarment scorecardProcurement questionsContractor lookup8(a) certification guide
Developers
Developer hubDocsAPI referenceQuickstartStatusChangelogSDKs & integrationsWebhooks
Research & guides
Research hubGuidesHealthcare provider dataExclusion & sanctions screeningProvider credentialing dataHealthcare data for AIHospital margin gapProvider access gapsGlossaryComparisonsCitationsWhy Fonteum
Company
AboutPressCustomersPricingContactEditorial policyCorrections
Trust & legal
TrustTrust markQualitySecurityPrivacy policyTerms of serviceAPI & MCP termsMedical disclaimer

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

© 2026 Fonteum LLC. All rights reserved.

·hello@fonteum.com

The U.S. healthcare graph AI can cite — every fact carries its source.

Every fact Fonteum serves carries a signed, re-checkable trust mark — source, as-of date, and an Ed25519 signature travel with the data. Re-check any fact at fonteum.com/verify · the trust-mark standard (W3C Verifiable Credentials 2.0, C2PA-aligned).
Request access→

The substrate, by the numbers

9.2Mgraph entitiesProviders, organizations, owners, and facilities
15.7Mlinked identifiersNPIs, CCNs, LEIs and more, resolved to entities
5Mgraph edgesSource-attested relationships between entities
44federal source familiesDistinct CMS, OIG, HRSA, FDA and peer datasets
35dataset pagesCitable, downloadable /data catalog pages
13reproducible studiesEach shipping the SQL behind its figures