Skip to content
FonteumThe Graph
DataResearchCare CompareThe DifferAttestAPI
See the proof
  • Data
  • Research
  • Care Compare
  • The Differ
  • Attest
  • API
See the proof
Fonteum
Products
The DifferAttestAPIFHIR API
Data
Care CompareResearchData catalogSources
Company
AboutPressEditorial policyCorrections
Legal
Privacy policyTerms of serviceMedical disclaimer

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

© 2026 Fonteum, Inc. All rights reserved.

The U.S. healthcare graph AI can cite — every fact carries its source.

Request access→
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-07 · methodology version moat-tracker/v1

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

Collected weekly. Anonymized. Auditable.

M-1
AI citations
0/ wk
target≥70% prompt citation by mo 12
as of 2026-06-09method →
M-3
Snapshot history depth
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
40snapshots
target52+ weekly snapshots by mo 12
as of 2026-06-08method →
M-4
FHIR API requests
Pending — key
target20,000+/wk by mo 12
awaiting FHIR request-log feed (fhir_request_logs)method →
M-5
Claimed listings
Pending — first run
target100+ claimed by mo 6
first reading scheduledmethod →
M-6
Press mentions
1/ wk
target20+ DR>50 domains by mo 12
as of 2026-06-08method →
M-19
Build velocity
224PRs / wk
target20+ PRs/wk
as of 2026-06-07method →
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. Each tile carries its 12-month target and an honest state: live once a reading exists, pending — first run when a self-contained metric is awaiting its next scheduled collection, or pending — key when a metric is gated on an external credential or upstream feed still to be provisioned. No placeholder zeros are ever shown. Full collection details, alert thresholds, and the underlying schema are documented in the methodology index.