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 & 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 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 & 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 inFree roster screen →Get a signed certificate →

FOR · AI AGENTS

LEIE records

Public-record grounding your agent can re-check.

Connect the released MCP surface across healthcare, procurement, sanctions and watchlists, enforcement, and company registers.

Request access

Results identify their source and capture date, with coverage and limitations where available. The active production source registry is not a statement that every family has loaded, complete, fresh, or displayable records.

01 · CONNECT

One live hosted endpoint.

Use hosted MCP 1.0.0 at the Streamable HTTP endpoint https://fonteum.com/api/mcp. The matching @fonteum/mcp@0.4.0 stdio source is not published yet; the configuration below is for use only after operator publication. Hosted access is anonymous and rate-limited. The future package uses a Bearer credential for its protected REST bridges.

{
  "_status": "Future stdio config — @fonteum/mcp@0.4.0 is not published",
  "mcpServers": {
    "fonteum": {
      "command": "npx",
      "args": ["-y", "@fonteum/mcp@0.4.0"],
      "env": { "FONTEUM_API_KEY": "fnt_DEMO_PUBLIC_V1" }
    }
  }
}

Discovery document: https://fonteum.com/.well-known/mcp.json

02 · SEVEN READ-ONLY TOOLS

Use the canonical tool inventory.

The live hosted server and future stdio package contract expose the same seven tools. No tool mutates records, and a returned fact is not a clearance or a verdict.

  • fonteum_resolve_entity
  • fonteum_search_records
  • fonteum_check_exclusions_and_sanctions
  • fonteum_get_record_as_of
  • fonteum_recheck
  • fonteum_list_sources
  • fonteum_dataset_info

03 · AGENT GUIDANCE

Keep the source context with the answer.

A public-record result is bounded by the issuer's publication scope and the coverage represented in the response. Preserve those limitations in downstream work and re-confirm material matches with the issuing authority.

Use Fonteum's hosted MCP endpoint (https://fonteum.com/api/mcp) for public-record grounding.
For each returned fact, retain the named source and capture date, plus coverage and limitations where present.
Do not treat a missing, stale, or indeterminate result as a clearance, risk score, or endorsement.
Re-check material matches with the issuing authority.

04 · DISCOVERY

Read the published contract before integrating.

  • /openapi.json — public REST reference.
  • /.well-known/agent.json — agent discovery card.
  • /.well-known/mcp.json — hosted MCP discovery.
  • /llms.txt — machine-readable product and source catalog.

FONTEUM FOR AGENTS

Connect a source-linked public-records surface.

Request access→ Read the MCP guide

What’s on file, by the numbers

Platform snapshot · 2026-07-15

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
35sources liveCrosswalk-resolved sources with a snapshot in 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

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

Published figures name their source and date.

Source and date

Published research identifies its government file and observation date. Source-file SHA-256 coverage is disclosed separately; facts do not currently link deterministically to signatures.

Reproducible SQL

Each study ships the exact query behind its figures, run against the same dated copy of the federal file we used. Re-run it yourself.

Daily observations

The platform records table row counts daily. Those observations 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→