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

Email-first. Self-service docs cover most pre-sale questions.

Response times are governed by your tier's SLA. We don't currently run a phone-tree or live chat — we run email, Slack (Standard+), and public documentation. The constraint here is a feature: a small founder-led team that responds personally beats a phone tree.

CONTACT BY PURPOSE
  • Pilot inquiries / new business
    pilot@fonteum.com
    Discovery calls, pilot scoping, agreement walkthrough. Goes direct to founder.
  • Sales / Standard + Enterprise tiers
    sales@fonteum.com
    Renewal questions, tier upgrades, contract scope changes.
  • Active customer support
    support@fonteum.com
    Pilot tier: 1 business-day response target. Standard tier: 4-hour business-hours target plus dedicated Slack channel. Enterprise: per signed agreement.
  • Security findings
    security@fonteum.com
    Acknowledgment within 2 business days. Full disclosure protocol on the /security page.
  • Press / media inquiries
    press@fonteum.com
    Methodology questions, dataset citations, journalist requests.
  • Data corrections
    corrections@fonteum.com
    Logged in our public corrections log. We do not silently change historical figures.
SELF-SERVICE

Most procurement questions are already answered

Before emailing, the following pages cover what most procurement and engineering teams ask first:

  • /methodology — published methods and limitations for supported surfaces
  • /data-provenance — nullable provenance fields and their limits
  • /sources — supported public source-detail pages with publisher cadence + ToS notes
  • /refresh-cadence — publisher cadence and dated loaded observations for selected sources
  • /research — published studies and downloads where supplied
  • /security — data scope, infrastructure, vulnerability reporting
  • /sla — uptime + response-time targets per tier
  • /terms — standard B2B terms; pilot agreements supersede
SEE ALSO

What’s on file, by the numbers

Platform snapshot · 2026-08-11

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