Skip to content
1,322,867 nurse-staffing records · CMS PBJ
fonteum
DataAPIResearchCompareRequest access →

Trust → Integrity → Verify

Re-hash any snapshot.

Every snapshot Fonteum publishes ships with a SHA-256 attestation. Look up any 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. Re-hash the bytes yourself; the result MUST equal the published hash.

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

How the re-hash flow works

  1. Look up the snapshot — GET /verify/<snapshot_id> returns the attestation envelope: content_hash,source_archive_url, cache_url (if mirrored), attested_at, and methodology_version.
  2. Download the bytes — fetch source_archive_url from the upstream agency, OR cache_url from the Fonteum 90-day mirror if the upstream URL has rotated.
  3. Re-hash — shasum -a 256 archive.csv. The result MUST equal content_hash. If it doesn't, the bytes were altered (or the source agency rotated their archive without publishing a new snapshot id) — the discrepancy is reportable to corrections@fonteum.com.
/chain — attestation chain head →/trust/integrity — full attestation index →/docs/cache — how the 90-day mirror works →

Compliance posture

Methodology · Corrections log · Editorial policy

fonteum

Product

  • Data
  • API
  • Methodology
  • Sources
  • Freshness
  • Citations

For buyers

  • AI agents
  • RAG developers
  • Compliance
  • Researchers
  • Developers

Reference

  • Compare
  • llms.txt
  • Agent card
  • Audit pack
  • Pilot intake
  • Research

Sourced from federal agencies. Fonteum, Inc., Delaware C-corp. © 2026.