VerApex — Verified conditions, proven at the Apex.

The time to fix a record is before it matters. VerApex captures what a source publishes as it's published, seals it to a public ledger, and fixes it to the point in time it describes — attributed, and beyond our reach to alter. When something turns on what was true then, the answer was settled before anyone had a reason to shade it.

Today: 102 river gauges on the Mississippi, Minnesota to the Gulf. Every other condition family we list says plainly what we don't capture.

102 stations live · Minnesota headwaters to the Gulf · sealed to a public ledger · NOAA & USGS

The problem

The data is free. The certainty isn't.

Every reading VerApex captures comes from an attributable source, and the record names which one. Anyone can go read that source themselves. What nobody can do afterwards is prove a particular reading existed, unaltered, at a particular moment.

How it's done today
01Records requestsWeeks of waiting for data that was public the whole time.
02Weather consultants$500–5,000 for a report the other side gets to contest.
03Expert witnesses$300–500 an hour to interpret numbers anyone can read.
04The nearest stationOften miles from the incident, with no disclosure of the distance.
05A single sourceOne reading, no corroboration, no way to show it wasn't touched.
How VerApex does it
01Captured liveRead within minutes of publication — not pulled from an archive months later.
02CorroboratedIndependent sources checked against each other. Disagreement is published, never averaged away.
03SealedContent-addressed and written to a public chain before anyone knew the question would be asked.
04AttributedEvery record carries its source URL. Check it yourself in ten seconds.
05Honest about gapsWhere nothing was published, we show nothing. We never interpolate a number into evidence.
How it works

Five steps between an instrument and an exhibit.

Nothing here is novel cryptography. It's ordinary discipline applied consistently — which turns out to be the rare part.

01

Observe

Capture at the source's own cadence. Nothing is padded between the readings it publishes, and nothing is interpolated where it published none. The record states its own resolution.

02

Corroborate

Count genuinely independent witnesses. A relay of another source is one voice, not two. Conflicts surface; they never resolve themselves.

03

Seal

Hash the record and write it to a public ledger. Once sealed, it persists independently of VerApex — we can't alter or remove it, and neither can anyone else.

04

Query

Ask by place and time — a town, an address, a date. Not by station ID. Nobody outside a river district knows what BTRL1 means.

05

Attest

On request, anchor the result set on-chain and issue a verification report: the hashes, the sources, and the steps a skeptic walks to check it.

Conditions

Water is where we started. Not where it ends.

Apex means the point — conditions at this point in time. The seal and provenance layer is common to every condition type: the bytes we sealed are the bytes the source served, and the hash proves it. What each new condition brings is its own measurement discipline — its instruments, its units, its reference frames — and whoever published the reading is named on the record.

Fourteen families mapped, one live. See every condition and its honest status → Nothing is sold for a lane we are not capturing.

14
Condition families
One live, thirteen mapped
2
Sources
Named on every record
0
Records we can alter
Sealed beyond our reach
Who it's for

When the answer has to hold up.

Six places where "what were the conditions?" is worth money, and where a contestable answer costs more than a verified one.

Maritime & admiralty

Grounding and allision

"The defendant says the fall was unforeseeable. Here's what the gauges published for the seventy-two hours before."

Stage, trend, and timing at the incident reach — sealed before suit was filed, with the source URL on every value.

Exhibit package · $999–2,999
Claims & adjusting

Flood causation

"The gauge published a crest at 3 a.m. The policyholder's account holds."

Arrival time, duration above each flood category, upstream lead time. Pay or deny on a defensible basis without an expert engagement.

Verified record · $299–999
Inland marine ops

Draft and tow planning

"The trough hits Vicksburg Thursday. Cut tow size now."

A wave takes days to travel — so an upstream reading is a downstream forecast. Threshold alerts on the reaches you actually run.

API + alerts · $299–999/mo
Parametric insurance

Trigger verification

"Forty-eight sustained hours above minor flood. Here's the window, sealed."

Insurer, insured, and reinsurer read the same record, and none has to take the others' word for it.

Settlement oracle · negotiated
Ports & infrastructure

Incident reconstruction

"Conditions at the structure, in the ninety minutes before impact."

What used to be a records request and a consultant is now minutes — with explicit gaps where no reading exists, never filled in.

Certified dataset · $4,999
Commodity & freight

Constraint propagation

"Navigability constraint reaches the elevators Friday."

Station readings become a moving constraint with an arrival time — and an attested history for post-trade review.

Dataset license · $10k–100k/yr
Where we started

All rivers lead to the bayou.

VerApex is built in Louisiana, on the water it knows best. The Lower Mississippi is a working corridor — deep-draft ports, barge traffic, storm exposure, and flood claims stacked on the same reach — where real money turns on what the water was doing and the answer gets argued in front of an adjuster or a judge.

That's not a marketing choice — it's a demanding place to be right, which makes it a fair test. The corridor is the first proving ground, not the boundary. Nothing in capture, corroboration, or sealing is river-specific; the Mississippi is where we made it defensible before selling a single record.

The federal government is stepping back from environmental monitoring at exactly the moment conditions are getting less predictable. Somebody has to keep the record. We'd rather it be somebody who lives downstream of it.

Baton Rouge → GulfAtchafalaya basinGulf IntracoastalBarataria & TerrebonnePort of South Louisiana
Pricing

Pay for the proof, not the data.

The readings are public and always will be. What you're buying is the assembly, the attestation, and a record the other side can check instead of contest.

Single matter

Verified record

$299 – $999
Attorneys, adjusters, individual claims
  • One location, one time window
  • Sealed records with source URLs
  • Nearest-station distance disclosed
  • Independent verification path included
  • Delivered as PDF and CSV
Request a record
Most requested

Exhibit package

$999 – $2,999
Law firms, carriers, complex matters
  • Multiple stations across a corridor
  • Time-lapse replay of the event
  • Exhibit-ready PDF and CSV
  • Independent verification path included
  • Direct line to the analyst who built it
Start a matter
Ongoing

API & alerts

$299 /mo and up
Operators, insurers, trading desks
  • Live and historical query access
  • Threshold alerting per location
  • Sealed records with source URLs
  • Bulk dataset licensing available
  • Settlement-oracle terms on request
Talk to us

Somebody has to keep the record.

Every day the archive gets one day deeper, and one day harder to argue with. The best time to have started was a year ago. The second best is before your next matter.