Skip to content
FonteumThe Graph

By use case

Exclusion screening (self-serve)First 25 NPIs — on screenExclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligence

By buyer

Compliance & riskJournalists & newsroomsDevelopers & AI teams

By industry

HealthcareProviders & facilitiesSanctionsOFAC / EU / UK / UN / OIG / SAMFederal contractingSAM · USASpending · FAPIIS

The capability layer

APIREST + bulk accessFor AI agentsModel Context Protocol serverFHIR R4 APIBulk exportAudit packSigned report artifacts; source facts remain separately citedReconciliationSource-vs-source diffsAI answers with sourcesHow records link upHistoryRetained versions for named sources

The differentiator

Coverage & sourcesThe catalogFreshnessMethodologyCare CompareFacility qualityAI answers, comparedBrowse all datasets →
Research

The dev on-ramp

DocsAPI referenceConnect your AI agent (MCP)One-paste installFHIR sandboxLive API surfaceQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inScreen 25 NPIs free →Buy $129 certificate →

Solutions

Exclusion screening (self-serve)Exclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligenceCompliance & riskJournalists & newsroomsDevelopers & AI teamsHealthcareSanctionsFederal contracting

Platform

APIFor AI agentsFHIR R4 APIBulk exportAudit packReconciliationAI answers with sourcesHow records link upHistory

Data

Coverage & sourcesFreshnessMethodologyCare CompareAI answers, comparedBrowse all datasets →
Research

Developers

DocsAPI referenceConnect your AI agent (MCP)FHIR sandboxQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inScreen 25 NPIs free →Buy $129 certificate →

Developer

Build on Fonteum’s public-records data

Fonteum provides REST and hosted MCP access to source-linked public records across healthcare, procurement, sanctions and watchlists, federal enforcement, and global company registers. FHIR R4 and bulk exports remain available where their documented contracts apply.

Reviewed by Dr. Jennifer Montecillo, MD, non-practicing medical reviewer. Last reviewed: June 2026 · Next review: December 2026

FHIR API

HL7 FHIR R4 US Core 6.1.0 provider directory. Practitioner, Organization, Location, PractitionerRole, HealthcareService — with SMART Backend Services auth and Bulk Data $export.

Read the reference→

Datasets

Browse source pages and manifest-led bulk exports. The manifest names each delivered file, its gzip compression, and its CSV columns.

Browse datasets→

Webhooks

Subscribe to provenance-stamped provider events. Receive HMAC-SHA256-signed POST notifications when LEIE or PECOS state changes for a tracked provider.

Register a subscriber→

What you can build

Integration patterns

  • EHR and clinical workflow integrations — pull practitioner directory data into scheduling, referral, and credentialing modules using the FHIR PractitionerRole resource.
  • Compliance dashboards — surface OIG LEIE exclusion status and PECOS enrollment state for providers in your network using the webhook stream.
  • Research pipelines — use FHIR Bulk $export for supported provider resources and the machine-readable bulk manifest for files that are currently delivered; source and format availability vary.
  • Quality-scoring applications — combine MIPS performance scores, Care Compare star ratings, and HCRIS cost data to build custom provider quality indices.

Developer FAQ

Common questions

What developer APIs does Fonteum offer?
Fonteum provides REST and hosted MCP access for public-record lookup, search, screening, and source context. FHIR R4 remains the healthcare interoperability surface. Bulk availability is manifest-led: only files with a delivered schema and compression format are listed.
Is authentication required to use the Fonteum FHIR API?
REST and MCP examples use an issued FONTEUM_API_KEY with Bearer authentication. Follow the current API authentication guide for access and rate-limit details; do not rely on a sample key.
What public records sources power the Fonteum API?
The active production registry spans healthcare, procurement, sanctions and watchlists, federal enforcement, intellectual property, securities filings, and global company registers. Results identify their named source and capture date; active registry status does not itself mean every family has loaded, complete, fresh, or displayable records.
How does Fonteum show source and capture context?
Where available, a result includes the named source, capture or snapshot date, methodology context, and limitations. This lets an integrator inspect the basis of a public-record fact without presenting the data as a derived risk score or endorsement.
Where can I find the FHIR CapabilityStatement?
The FHIR CapabilityStatement is published at /api/fhir/metadata. It enumerates 5 USCDI v3 Provider resources: Practitioner, Organization, Location, PractitionerRole, and HealthcareService. The statement conforms to US Core 6.1.0 and includes SMART Backend Services security extensions.

Related documentation

  • /docs/fhir— FHIR R4 provider directory API reference
  • /docs/bulk-export— Bulk Data $export implementation guide
  • /docs/identity— Federated identity resolution (NPI ↔ PECOS-ID)
  • /docs/webhooks— Provider event webhook subscription
  • /for/developers— Fonteum for developers — use cases and access
  • /developers— Developer hub — REST, MCP, FHIR, and SDKs
  • /platform— Platform — the full capability layer

What’s on file, by the numbers

Platform snapshot · 2026-07-18

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
83sources with dataDistinct snapshot source IDs with at least one positive record count
71fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

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

Read the full provenance and attestation methodology →

Fonteum
Platform
Platform overviewAPIFor AI agents (MCP)FHIR R4 APIBulk exportAudit packReconciliationAI answers with sourcesHow records link upHistory
Solutions
All solutionsExclusion & sanctions screeningCredentialing & enrichmentAudit evidenceProvider data for AI / RAGUse casesM&A & network diligenceCompliance & riskJournalists & newsroomsDevelopers & AI teams
Data & sources
Coverage & sourcesBrowse all datasetsState Medicaid exclusionsFreshnessMethodologyCare CompareNursing homesRecall recordsSanctions screeningOIG LEIE listOwnershipStaffingDeficienciesSpecial Focus Facilities
Federal contracting
OverviewAwards during active exclusionFederal debarment scorecardProcurement questionsContractor lookup8(a) certification guide
Developers
Developer hubDocsAPI referenceQuickstartStatusChangelogSDKs & integrationsWebhooks
Research & guides
Research hubLearnHow it worksGuidesHealthcare provider dataExclusion & sanctions screeningProvider credentialing dataHealthcare data for AIHospital margin gapProvider access gapsGlossaryComparisonsSourced data vs plain LLM answersCitationsManifestoWhy Fonteum
Company
AboutPressCustomersPricingContactEditorial policyCorrections
Trust & legal
TrustTrust markQualitySecurityPrivacy policyTerms of serviceAPI termsMedical disclaimer

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

© 2026 Fonteum LLC. All rights reserved.

·hello@fonteum.com

A public-records graph that exposes source and observation metadata where supplied.

Fonteum's provenance ledger contained 26.2M source-linked facts on July 12, 2026. All but 14 carried a source-file SHA-256; 0 linked deterministically to a signature. Inspect a supplied snapshot id at fonteum.com/verify · source-mark coverage and limitations.
Request access→