Skip to content
fonteum
DataAPIRisk SignalsResearchCompareSnapshotsRequest access →

Compliance posture

Methodology · Corrections log · Editorial policy

fonteum

Product

  • Data
  • API
  • Methodology
  • Sources
  • Freshness
  • Citations
  • Moat metrics

For buyers

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

Reference

  • Compare
  • llms.txt
  • Agent card
  • Audit pack
  • Quality scorecard
  • Pilot intake
  • Research
  • Press & media

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

Fonteum is a US healthcare provenance registry.

About Fonteum ›

Fonteum is a US healthcare provenance registry that publishes signed, chain-of-custody-attested research and data pages on Medicare, Medicaid, and federal regulator datasets, drawing from 22 federal source families across CMS, OIG, HRSA, AHRQ, and HHS.

Request access→
1,322,867 nurse-staffing records · CMS PBJ
Moat metrics

The moat, measured. Not a deck — a timestamp.

Fonteum instruments its own growth. These six metrics are collected automatically, stored append-only, and published here rolled-up and anonymized. Every number is a query against a production table, not a screenshot.

Last updated: 2026-06-03 · methodology version moat-tracker/v1

Source: Fonteum Moat Tracker (append-only)·Snapshot: 2026-06-03·Method: moat-tracker/v1
Six headline metrics

Collected weekly. Anonymized. Auditable.

M-1
AI citations
Not reported
awaiting first collectionmethod →
M-3
Snapshot history depth
Not reported
awaiting first collection
Methodology

How each number is measured.

M-1 · AI citations
A locked weekly set of real user questions is sent to ChatGPT, Perplexity, Claude, and Gemini. Each response is scanned for Fonteum URLs. The headline is the number of citations across all queries that week.
M-3 · Snapshot history depth
For each federal source family we hold, we count distinct dated snapshots. The headline sums those across families — a proxy for how much history exists that a fresh competitor cannot backfill.
M-4 · FHIR API requests
Requests to the live FHIR R4 endpoints are tallied weekly and classified by consumer (AI agents, developers, browsers). The headline is total weekly requests.
M-5 · Claimed listings
The cumulative count of provider/facility listings claimed by their owners — the network-effect curve. No owner identities are published, only the total.
M-6 · Press mentions
Instrumented, not asserted

A live FHIR R4 API, a public SHA-256 attestation chain, and an open methodology back every Fonteum number. These metrics show the asset compounding — in data anyone can re-query.

FHIR R4 API
US Core 6.1.0
live · /api/fhir
Attestation chain
SHA-256 signed
public · /chain
Methodology
version v2026.05.0
public · /methodology
Provenance
14-tuple per field
source · date · confidence
Source registry
22 federal families
all primary-source · /sources
method →
M-4
FHIR API requests
Not reported
awaiting first collectionmethod →
M-5
Claimed listings
Not reported
awaiting first collectionmethod →
M-6
Press mentions
Not reported
awaiting first collectionmethod →
M-19
Build velocity
Not reported
awaiting first collectionmethod →
Distinct news/media URLs mentioning Fonteum, discovered weekly. The headline is the count of unique mentions that week.
M-19 · Build velocity
Pull requests merged to the main branch in the trailing 7 days, read directly from version control — a founder-execution signal.

Metrics are append-only and timestamped at collection. Where a metric has not yet produced a reading, it renders Not reported rather than a placeholder value. Full collection details, alert thresholds, and the underlying schema are documented in the methodology index.