Primary source verificationSign in

Healthcare credential verification takes 30 days. Credool does it in 24 hours and writes the proof to the blockchain permanently.

24h

Verification cycle

50

State boards in programme

15:00

QR code lifetime

0

Records editable after anchoring

How it works

01

Credool Loop

Crawls state medical boards and the NPDB every 24 hours.

Every attempt ends in one of eight explicit outcomes. A board that times out is recorded as a transport failure and the credential is marked stale. It is never silently reported as still verified.

02

Credool Ledger

Batches verified records into a Merkle tree and anchors the root on Polygon.

One 32 byte root per batch, written once, with no update path in the contract. Any party can rebuild the tree from the published proof and check the root against the chain without asking Credool.

03

Credool Wallet

Gives the clinician a passport app that issues 15 minute verification codes.

Codes expire through Redis key expiry, not a timestamp the holder presents. A screenshot passed to someone else stops working before the end of a shift handover.

Why the anchor matters

A credentialing file in a hospital system records that a check happened. It does not prove when, and it can be edited by anyone with database access. That gap is what a plaintiff's attorney works on after a negligent credentialing claim.

An anchored Merkle root removes the gap. The hash of the credential state at the moment of verification sits in a public block with a timestamp nobody controls. The hospital can prove what it knew and when it knew it, and so can the clinician.

What is on chainPublic
Merkle root
32 bytes per batch
Leaf count
Credentials in the batch
Block timestamp
Set by the network, not by Credool
Submitter address
The ledger service signer

Not on chain

No name, no NPI, no licence number, no date of birth. A leaf is only meaningful to someone who already holds the record it describes.