Skip to main content
xcircl
Data · sources

Every field traces to an official record.

Our outward data is built from authoritative records — not star ratings, not ads. Each field carries the source it came from and the date we checked it, so you can stand behind what you build on it.

NPPES / NPI Registry

CMS · Provider identity

The official U.S. registry of healthcare providers. Anchors a provider’s identity and NPI.

namenpiaddress

LegitScript

LegitScript · Healthcare-merchant certification

Certification status for healthcare and telehealth merchants. Shown only with a verification date.

legitscript_status

State licensing boards

State medical / professional boards · Licensure

Active professional licensing on file, attributed per state. Reported vs. board-verified is labelled distinctly.

license_statuslicense_states

FDA

U.S. Food & Drug Administration · Enforcement screen

Screened against FDA warning letters. A provider is “clear” only when we’ve run the screen; “flagged” when a letter is on file.

fda_status

CMS Care Compare

CMS · Quality data (select verticals)

Official quality and certification data for applicable verticals (e.g. senior care). Added per vertical as coverage expands.

quality_signals

Merchant-submitted

The provider · Commercial details

Pricing and service details a provider submits through a claim. Always labelled provider-reported until independently verified.

pricehoursservices
The guardrail

What we won’t do

  • No platform scraping in outward fields. Third-party directory ratings never become an outward xcircl fact.
  • No invented values. A field we can’t source is returned empty or “not yet verified” — never filled by a model.
  • Verified means verified. A signal is only marked verified when we hold both a source and a verification date.

Source-data migration is ongoing. We describe our method and sources here; we publish specific verified-coverage figures on the coverage page as they grow, rather than overclaiming today.

See it in the data

Browse a real sample, or read how the API exposes source + timestamp per field.