AeroBrief · Imperial AI Agent Hackathon · Solana × CoralOS track

The customer is software.
And it can't eyeball the data it buys.

Agent commerce is live: agents already pay per call for data and compute. But every agent market settles on "something was delivered", not "the right thing was delivered." An agent that pays for a number has no way to squint at it. That is the oracle problem, in miniature, at the bottom of the whole agent economy.

3.1Magent payments on Base in 30 days, and none of them audited what they bought

Why nowmachine buyers scale faster than trust does

What it sells: a flight briefing an arbiter can re-derive

deliverService('brief OMDB-OLBA-midsize') returns a dispatch briefing: great-circle distance, initial bearing, block time, fuel with 45-minute reserve, alternates within 300 nm. Computed from 49,208 real airports (OurAirports) and published performance profiles. Deterministic on purpose: every number is derivable from the deliverable's own coordinates.

Why they pay

AI trip-planning and charter-ops agents need this before quoting any flight
Flight-support desks sell exactly this to operators today, human-to-human
Priced per call in SOL: 0.0002 to 0.0009 per briefing in the demo market

Grounded in real practice

The briefing mirrors what real flight-support desks sell operators every day, human-to-human
The mainnet twin already exists: AgentGate sells airport/route data to agents over x402 (USDC on Base)

The economy: three personas, one adversary

A buyer agent broadcasts a route over CoralOS. Three LLM sellers compete: dispatch-basic (correct, minimal, cheap), dispatch-premium (alternates + fuel plan + advisories, bids on value), and dispatch-shady, which undercuts everyone and pads distances 8%. The adversary is in the demo on purpose.

WANT ─▶ BID ─▶ AWARD ─▶ DEPOSITED ─▶ DELIVERED ─▶ AUDIT ─▶ RELEASED │ │ │ │ │ │ │ ops 3 LLM best escrow briefing arbiter escrow pays buyer sellers value locked on computed recomputes the seller asks compete pick devnet from real every or REFUNDED (arbiter- airports number when it lies gated)

Proof: the moment the agent decides not to pay

Before signing arbitrate_release, the arbiter recomputes distance, bearing, block time, fuel and alternate distances from the delivered coordinates with an independent copy of the math. Both outcomes settle on-chain, live on devnet, Explorer-verifiable:

ARBITER AUDIT · PASS: verified 5/5 checks → release → seller paid dispatch-basic, VIDP→OMDB: every number recomputed clean. Live devnet tx: 4MKeafvz…HbwRD

ARBITER AUDIT · FAIL: distance claimed 3056.5 nm, recomputed 2830.1 nm (8.00% off) → release withheld → refund dispatch-shady loses the sale and the fee. Fraud is not moderated away; it is priced out by settlement. Live devnet tx: 4DgyxwDH…8Zhm

Working demo: one command per pane · settled live on devnet · 98 unit tests across runtime, sellers, buyer, feed, console

Any deliverable that can be re-derived can settle this way

Routes, unit conversions, quotes, market data, oracle reads: whenever the payload carries enough to recompute the claim, escrow can release on provable correctness instead of delivery. AeroBrief is the flight-ops instance of a general settlement pattern the agent economy is missing.

Team

An independent builder pairing aviation-operations domain knowledge (dispatch, fuel, permits) with agent-economy engineering. Domain data, domain pricing, domain fraud patterns, all real — and already selling aviation data to agents on mainnet via AgentGate.

The customer is software.And it can't eyeball the data it buys.