Skip to content
FonteumPublic-records evidence
Screen 25 NPIs free →Buy $129 certificate →
Documentation

Fonteum developer documentation

Reference documentation for Fonteum's REST and hosted MCP surfaces, FHIR R4 provider directory, bulk exports, webhooks, and identity resolution. The platform spans public-records domains including healthcare, procurement, sanctions and watchlists, enforcement, and global company registers; documented results include the source and capture context available for each source and endpoint.

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

APIs

  • HL7 FHIR R4 US Core 6.1.0 — Practitioner, Organization, Location, PractitionerRole, HealthcareService. Da Vinci PDex + SMART Backend Services.

  • Free .edu/.gov tier for academic and government researchers. Citation spec, rate limits, and authentication.

  • Natural-language semantic provider search. NPI lookup, specialty filter, and location-based queries.

  • Screen NPIs through the live REST endpoint from a shell or GitHub Actions workflow step; source and date context is returned where the endpoint supplies it, and fields can be null.

Data access

  • Manifest-led downloads. The manifest names each currently delivered file, its gzip format, and its CSV columns.

  • DCAT-US 3.0 catalog and Google Dataset Search submission documentation for all Fonteum datasets.

  • CMS Medicare Inpatient utilization reference — 10th source family. Hospital Performance dataset equivalent, free.

  • CMS Medicare Outpatient utilization reference — 11th source family.

Identity + provenance

  • NPI ↔ PECOS-ID canonical identity layer. Cross-source entity resolution and chain attestation.

  • ORCID iD linkage for researcher authentication and citation attribution.

  • Nullable provenance-field specification and the separate scope of snapshot attestations.

  • Ed25519 chain link hashing and snapshot witness signature scheme.

Events + integrations

  • Load the seven Fonteum tools into LangChain or LlamaIndex through the hosted MCP endpoint or REST API. TypeScript and Python examples use an issued key.

  • WebhooksStable

    Subscribe to HMAC-SHA256-signed provider events. LEIE and PECOS state changes delivered to your endpoint.

  • Automated AI citation detection and citation chain monitoring for published research studies.

Operations

  • Complete inventory of all Fonteum cron jobs and Inngest functions with schedules and ownership.

  • ISR revalidation windows, CDN caching strategy, and per-route cache policies.

Documentation FAQ

What documentation does Fonteum publish?

Fonteum publishes documentation for REST, hosted MCP, FHIR R4 provider-directory interoperability, manifest-led bulk downloads, webhooks, identity resolution, and public-record sources. Active production registry status does not itself mean every family has loaded, complete, fresh, or displayable records.

Which FHIR implementation guides does Fonteum support?

Fonteum's FHIR R4 API conforms to US Core 6.1.0, the Da Vinci PDex Provider Directory IG, and the HL7 FHIR Bulk Data Access v2.0.0 implementation guide. All five USCDI v3 Provider resources are enumerated in the CapabilityStatement at /api/fhir/metadata.

How do I access Fonteum bulk datasets?

The manifest at /api/v1/bulk/manifest.json lists only bulk files that are currently delivered, including each download URL, gzip compression, CSV columns, and source context. See /docs/bulk-export for the complete download guide.

What is the rate limit for the Fonteum API?

REST and MCP examples use an issued FONTEUM_API_KEY with Bearer authentication. Consult the API authentication guide for the current access and rate-limit policy.

Does Fonteum provide provenance metadata in API responses?

Where available, API results include source and capture context such as the named source, snapshot or capture date, methodology context, and limitations. Fields can be null or absent by response, and they do not establish an individual-field signature.

What’s on file, by the numbers

Platform snapshot · 2026-07-24

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
79fresh 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