VerifyHub is the neutral, standards-based quality engine. It turns competing quality claims into a verified fact. That fact feeds straight into the escrow release conditions, before anyone can argue about what "meets spec" means.
The Problem It Solves
Specification naming differs across standards. Industrial labs still exchange results as PDFs with no standard API. Disputes over quality are the single most common reason swaps fail before they settle.
How it runs
VerifyHub runs a staged verification pipeline built for low-volume, high-value, latency-sensitive lab data.
A three-stage pipeline resolves material names across competing naming systems against a structured material reference set. The stages are an exact lookup, a full-text search, then semantic matching.
Work orders route to accredited third-party labs matched to the material category, for example petroleum, minerals or rare earths.
LABS: ACCREDITED THIRD-PARTY ONLYResults come from many LIMS platforms. No universal API standard exists across them. VerifyHub ingests the results and normalises them into one standard format, whatever the source.
VerifyHub publishes the quality-accepted verdict as one of the needed escrow release conditions. VerifyHub sets the flag. The settlement engine owns the release decision.
Two Views, One Verdict
Traders get a clear quality verdict. Where relevant, they also get a volume adjustment factor that expresses the quality differential. There is nothing more to interpret.
Quality managers can drill into the complete certificate of analysis and test detail behind every verdict.
Design Targets
Specification-matching lookup across the material reference set (design target)
Closed verdict shape: a boolean gate plus a volume adjustment factor
Target trader interaction time across the full verification lifecycle
Third-party labs only, routed by material category — never self-certified results
Related
Request a walkthrough and see a verification run in the demo.