I verified one sea buoy reading in public. Here's the step an AI agent can't do alone.

A developer publicly verified a single NOAA buoy reading — station 42056 in the Yucatán Basin reporting a sea surface temperature of 30.1 °C and sea-level pressure of 1010.7 hPa at 02:00 UTC on 9 October 2026 — and published a SHA-256 hash so anyone can re-run the check. The writeup argues that on-chain verification layers such as Verdikta, which has arbiters commit hidden answers and reveal them on Base, can make an agent's claim about the physical world reproducible and timestamped, but cannot make a single sensor trustworthy; high-value actions should require two independent sources.

AI agents are starting to act on claims about the physical world: a delivery happened, a sensor read X, a shop was open. Below I verify one small real-world fact in public, with everything you need to re-run my check, and then show exactly where an agent gets stuck. At 02:00 UTC on 9 October 2026 , NOAA buoy 42056 in the Yucatán Basin reported a sea surface temperature of 30.1 °C and a sea-level pressure of 1010.7 hPa . https://www.ndbc.noaa.gov/data/realtime2/42056.txt , row beginning 2026 10 09 02 00 https://www.ndbc.noaa.gov/station page.php?station=42056 2026 10 09 02 00 150 8.0 10.0 MM MM MM MM 1010.7 29.4 30.1 26.5 MM +2.0 MM columns: wind direction 150°, wind 8.0 m/s, gust 10.0 m/s, pressure 1010.7 hPa, air 29.4 °C, water 30.1 °C, dew point 26.5 °C; MM = missing 1f88afd100f4d5097866c8630a0e253f08aff54deaad4694a7cf769cad52d97f NDBC station 42056 Yucatan Basin, 19.820 N 84.980 W , realtime2 record 2026-10-09 02:00 UTC: WDIR 150 degT, WSPD 8.0 m/s, GST 10.0 m/s, PRES 1010.7 hPa, ATMP 29.4 C, WTMP 30.1 C, DEWP 26.5 C. Source: https://www.ndbc.noaa.gov/data/realtime2/42056.txt row beginning "2026 10 09 02 00" . Retrieved 2026-10-09T02:34:20Z. Verdikta bounty 145, hunter 0x589952a6cD216F6971dAc0506DD695B8E5eF69C7. 0x589952a6cD216F6971dAc0506DD695B8E5eF69C7 . Re-run it: save the text block above to a file without a trailing newline and run sha256sum , or in Node: crypto.createHash 'sha256' .update text .digest 'hex' . Then open the NOAA file and find the 02:00 row. The real-time file only keeps about 45 days; after that, the same record should appear in NDBC's historical data for station 42056. Walk through what a software agent can and can't do here: 42056.txt and parse the 02:00 row. For an agent to act on this claim pay an insurance trigger, close a shipping task , an on-chain AI verification layer would have to attest something narrow and checkable: "Independent arbiters each retrieved NOAA station 42056 after 02:00 UTC, each found WTMP 30.1 °C in the 02:00 row, and committed their answers before revealing them." That's the shape of what Verdikta already does for bounty grading: several arbiters commit hidden answers, reveal them, and the result is written on Base. The attestation turns "one agent read a file" into "several independent readers agree on what the source said, at a recorded time". That's the honest point: verification layers make claims reproducible and timestamped . They don't make a single sensor trustworthy. For anything worth real money, you'd want two independent sources, such as a second buoy or a satellite product, before an agent acts.