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

Trust → Integrity → Verify

Re-check a snapshot commitment.

This tool applies to snapshot rows that have an attestation. Look up an attested snapshot by its numeric id and you'll get the full envelope: the upstream archive URL, the published content hash, the attested-at timestamp, and (when available) the cached mirror URL on Fonteum's 90-day rolling S3 cache. Only a raw-file SHA-256 commitment can be compared directly with re-hashed archive bytes; other commitment versions require their named methodology.

Re-check it yourself

Look up a snapshot id to see the source, date, digest, and chain fields that record actually returns. Digest comparison checks archive bytes; signature status is shown separately. No account needed.

snapshot field guide
source shown when returned
date saved shown when returned
sha-256 shown when returned
chain signature shown only when returned

Or run the full flow at /verify · curl /verify/<id>

Or look one up the plain way

Or: curl https://fonteum.com/verify/<id>

How the raw-file SHA-256 re-hash flow works

  1. Look up the snapshot — GET /verify/<snapshot_id> returns the available snapshot fields, which can include content_hash, source_archive_url, and cache_url. Any of those fields can be null.
  2. Download the bytes — fetch source_archive_url from the upstream agency, OR cache_url when that snapshot record provides one.
  3. For a raw-file SHA-256 commitment, re-hash — shasum -a 256 archive.csv. When both the bytes and content_hash are available, compare them. Do not apply this byte comparison to another hash version. A mismatch means the downloaded bytes do not produce the recorded digest; report it to corrections@fonteum.com.

What’s on file, by the numbers

Platform snapshot · 2026-08-26

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