Skip to content
FonteumPublic-records evidence
Screen 25 NPIs free →Buy $129 certificate →
Docs · Agent integrations

Connect your agent to public records it can cite

Fonteum provides nine read-only MCP tools across healthcare, federal procurement, sanctions and watchlists, enforcement, and corporate and securities records. Every response carries the same four citation keys; unavailable source file, date, or digest values stay null.

Hosted MCP 1.1.0: https://fonteum.com/api/mcp · REST base: https://api.fonteum.com/v1 · REST demo: Authorization: Bearer fnt_DEMO_PUBLIC_V1

The nine canonical tools

ToolArgumentsReturns
fonteum_lookup_npinpiLook 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_contractorexactly one of uei or cageLook 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_providersvertical, state, county?, limit?Search 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_exclusionnpiCheck 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_sanctionsnameSearch 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_historyas_of, exactly one of uei or cageLook 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_snapshotsnapshot_id?Recheck 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_sources—List 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_info—Get 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.

MCP

Use the live hosted 1.1.0 endpoint when your client supports streamable HTTP. The matching @fonteum/mcp@0.5.0 stdio source is pending operator publication; npm currently serves 0.4.0. The configuration below is for use only after operator publication. Both contracts use the same nine tool names and annotate every tool readOnlyHint: true. Hosted access is anonymous and rate-limited.

{
  "_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}" }
    }
  }
}

Successes and errors return JSON text plus matching MCP structured content. source_file, as_of_date, snapshot_digest, and verifiable_url are always present at the top level. The first three are nullable; a composite response does not invent one file or digest for many sources.

The future package contract uses https://fonteum.com/api as its REST base and FONTEUM_API_KEY for Bearer auth. Hosted clients point to https://fonteum.com/api/mcp. Anonymous hosted access is rate-limited; a separately issued hosted transport key, when available, uses x-fonteum-mcp-key and is distinct from the REST Bearer credential.

REST

Use REST when you need an application-local wrapper around a specific endpoint. Keep account keys server-side and send the standard Bearer syntax. The demo fixture below is runnable without signup.

const apiKey = process.env.FONTEUM_API_KEY ?? "fnt_DEMO_PUBLIC_V1";

async function getNpiRecord(npi: string) {
  const response = await fetch(
    "https://api.fonteum.com/v1/npi/" + encodeURIComponent(npi),
    {
      headers: {
        Authorization: "Bearer " + apiKey,
        Accept: "application/json",
      },
    },
  );
  if (!response.ok) throw new Error("Fonteum API " + response.status);
  return response.json();
}
import os
import requests

api_key = os.environ.get("FONTEUM_API_KEY", "fnt_DEMO_PUBLIC_V1")

def get_npi_record(npi: str) -> dict:
    response = requests.get(
        "https://api.fonteum.com/v1/npi/" + npi,
        headers={
            "Authorization": f"Bearer {api_key}",
            "Accept": "application/json",
        },
        timeout=30,
    )
    response.raise_for_status()
    return response.json()

Authentication and response metadata

  • Demo access. The read-only fnt_DEMO_PUBLIC_V1 credential uses 20 requests/minute and 100 requests/day per trusted source IP.
  • Account access. Create an account at /account/signup, accept the API Terms, and issue a fnt_… key from the account dashboard.
  • Source context. Cite only populated values. A null source_file, as_of_date, or snapshot_digest must remain null downstream.
  • Read-only. The nine MCP tools do not mutate Fonteum data.

See also

What’s on file, by the numbers

Platform snapshot · 2026-07-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
78fresh 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