Case No. FP·2026 / Jurisdiction: United StatesStatus: Ongoing
Fundprint.Who funds your therapist
The Machine / How it works

How the record is built

Fundprint is not a hand-kept list. It is a deterministic pipeline: the same public inputs run through the same code produce the same record, and every published claim carries the document that proves it.

The Fundprint ownership engine, Figure 1A schematic of the five-stage pipeline. Public records from the NPPES registry and owner directories enter at the intake on the left, pass through five machined stages, Acquire, Store, Resolve, Validate and Publish, along a drive shaft, and exit on the right as verified clinic to owner to parent-firm ownership chains.FIG. 1 / THE OWNERSHIP ENGINEDETERMINISTIC / SOURCEDNPPES+ DIRECTORIESIAcquire649 + 255 records inINTAKEIIStorepgvector + snapshotsSNAPSHOTIIIResolveclinic → owner → firmMATCHIVValidate95% hand-checked gateGATEVPublishverified chains outEMITCLINICOWNERFIRMVERIFIEDPIPELINE: 5 STAGES
1
Exhibit / The five stages

One machine, start to finish

  1. IAcquire
    649 + 255 records in

    The federal NPPES provider registry (649) plus owners' own machine-readable location directories (255). Every page is fetched and content-hashed on the way in.

  2. IIStore
    pgvector + snapshots

    Nothing advances without a stored, hashed copy of the document behind it. Names are embedded as vectors in Postgres so the resolver can reason over them.

  3. IIIResolve
    clinic → owner → firm

    A deterministic name matcher links clinics to owner entities and owner entities to their parent financial firm. Chain confidence is the weakest link along the chain.

  4. IVValidate
    95% hand-checked gate

    Confidence floors and a 95% hand-validation gate. Contradicted or under-confidence claims are quarantined, not published. Over-matched brand names are rejected.

  5. VPublish
    verified chains out

    Only claims that clear validation are written to the frozen snapshot this site reads. Every published claim carries the source that proves it.

2
Exhibit / Why two registries

Where the clinics come from

One source is NPPES, the federal provider registry. Anyone can download it and check us. But it enumerates registrations, not centers: a chain that runs forty centers under three identifiers appears as three. And nothing obliges a company to withdraw a registration when a center closes, so the registry also reports places that are no longer there.

The other is the operator’s own public list of its centers, read from the structured data its site publishes for search engines, never scraped from rendered prose. Where that list is complete, it wins. It is what the company tells parents today, and it corrects the registry in both directions at once: it names centers the registry never saw, and it declines to name the ones that closed.

Both are de-duplicated on one key, the street address and ZIP within an owner, so a center appearing in both is counted once.

Clinic-existence sources
Operator’s own directory1,573
NPPES registry alone182

A center matching no tracked owner is left unlinked. A registration an operator’s own complete directory does not list is quarantined, not deleted.

3
Exhibit / The integrity bar

What we refuse to do

  • Never assert without a source

    Every published ownership claim traces to a content-hashed snapshot of a public document. A claim missing its source does not publish, at any confidence.

  • Verify the current owner

    Ownership turns over. We cite the owner today, not a stale deal, and drop owners we cannot currently substantiate.

  • Reject over-matches

    A brand name is only a string, and two companies can share one. “Hope Bridge” matches Hope Bridge Counseling, which is a different business. Names too generic to tell apart are refused, and an operator’s own directory is what catches the rest.

  • Label honestly

    Pension funds and family offices are named as what they are, not folded into private equity.

4
Exhibit / Reproducible by design

Pinned, versioned, open

The site ships a frozen snapshot, not a live feed: what you read is a reproducible state, dated and version-pinned, so a screenshot dates itself. The methodology is versioned separately and the whole pipeline is open source.

dataset 2026.07-betamethodology 2026.07-statefile-v1read the full methodologyhow provenance works