Skip to content
FonteumPublic-records evidence

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 carry nullable source, as-of, snapshot-digest, and re-check context, with coverage and limitations where available. Preserve null values rather than inferring missing evidence. 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.1.0 at the Streamable HTTP endpoint https://fonteum.com/api/mcp. The matching @fonteum/mcp@0.5.0 stdio source is not published yet; it is pending operator publication. npm currently serves 0.4.0. The configuration below is for use only after 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.5.0 is pending operator publication; npm currently serves 0.4.0",
  "mcpServers": {
    "fonteum": {
      "command": "npx",
      "args": ["-y", "@fonteum/mcp@0.5.0"],
      "env": { "FONTEUM_API_KEY": "${FONTEUM_API_KEY}" }
    }
  }
}

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

02 · NINE READ-ONLY TOOLS

Use the canonical tool inventory.

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

  • fonteum_lookup_npiLook up a US healthcare provider by 10-digit NPI in CMS NPPES and return the available provider record plus exclusion and program-integrity context. Returns dated source context; source_file and snapshot_digest are nullable when no single retained snapshot represents the response. Use for NPI lookup, provider identity, taxonomy, practice-location, or provider due-diligence questions.
  • fonteum_lookup_contractorLook up a US federal contractor by UEI or CAGE in available SAM.gov, USASpending, FAPIIS, and FAR 4.18 records. Returns dated source context; source_file and snapshot_digest are nullable when no single retained snapshot represents the response. Use for contractor identity, registration, award, responsibility, or ownership due diligence.
  • fonteum_search_providersSearch US healthcare providers in loaded CMS NPPES specialty caches by vertical and state, with optional county context. Returns dated source context and up to 100 records; source_file and snapshot_digest may be null. Use for provider discovery by specialty and geography.
  • fonteum_check_exclusionCheck whether a US healthcare provider by NPI appears in available exclusion or integrity sources: OIG LEIE, SAM.gov exclusions, available state Medicaid lists, OIG Corporate Integrity Agreements, and CMS Civil Money Penalties. Returns dated source context and fail-closed coverage; source_file and snapshot_digest may be null for the multi-source result. Use for exclusion screening, provider or vendor due diligence, or any ‘is this NPI excluded?’ question.
  • fonteum_search_sanctionsSearch a person or organization name across available sanctions and watchlist data from OFAC, the EU, the UK, and the UN, plus named exclusion sources held by Fonteum. Returns dated matches with source context; source_file and snapshot_digest may be null for the multi-source result. Use for sanctions screening, entity due diligence, or any ‘is this entity sanctioned?’ question.
  • fonteum_lookup_contractor_historyLook up a US federal contractor record as of a requested date using UEI or CAGE. Retained history is currently limited to USASpending award rows; other fields may be current, absent, or nullable. Returns dated source context. Use for historical award research or contractor change questions.
  • fonteum_recheck_snapshotRecheck a Fonteum snapshot by snapshot id and return its as_of_date, snapshot_digest, public verifiable_url, and source_file only when explicit retained-artifact metadata is available. Without an id, returns chain status without treating the chain head as a snapshot digest. Use for snapshot integrity checks, citation support, or reproducing a retained source file.
  • fonteum_list_sourcesList Fonteum’s public-record source catalog with available authority, vertical, cadence, official URL, and separately dated platform coverage. Catalog presence does not prove loaded, fresh, or complete coverage. Use for source discovery, coverage questions, or choosing a dataset before a lookup.
  • fonteum_get_dataset_infoGet Fonteum API and MCP methodology, provenance-field definitions, generated source catalog, and separately dated platform coverage. Field population varies by source and response. Use for interpreting Fonteum outputs, citation fields, dataset limitations, or integration planning.

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. All four source-context keys are always present; source_file, as_of_date, and snapshot_digest can be null. Preserve those limitations 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 source_file, as_of_date, snapshot_digest, and verifiable_url exactly as returned; do not fill null values.
Do not treat a missing, stale, or indeterminate result as a clearance, risk score, or endorsement.
Treat a snapshot_digest as snapshot-level evidence, never as a signature over each returned fact.
Re-check material matches with the issuing authority.

04 · DISCOVERY

Read the published contract before integrating.

FONTEUM FOR AGENTS

Connect a source-linked public-records surface.

What’s on file, by the numbers

Platform snapshot · 2026-08-30

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
16fresh 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 →

Request access