GM gVAN
Ground truth often takes weeks to arrive.
Here is what it takes to learn what one specific place looks like today:
→ Mapping van: schedule a route, wait for the drive, then wait for processing
→ Sensor box: design it, manufacture it, ship it, book an installer, and hope the density shows up
→ A phone: already in someone's pocket near the place, on a street they walk every day
@vangrid_io is built on the third option. It is a DePIN for spatial data where the node is the device a contributor already carries, so there is no unit to build, no pallet to track, and no installer to schedule. A requester names a place and funds a bounty in USDC. Someone nearby opens the app and walks a slow orbit, and a preview comes back first so a weak pass gets caught before the full 3D reconstruction. Faces and license plates are blurred on the device, each capture is fingerprinted at record time, and the batch is anchored on Base through EAS so the origin can be verified onchain.
The requester can also be software. An AI agent can book a flight and file an invoice, but it cannot walk a loading bay. Through Vangrid's bounty API, the agent posts a job with one HTTP call, pays in USDC through x402 on Base or Arc, and a person nearby takes the work. Funds sit in escrow until the agent accepts a submission, and they return in full if the job is cancelled or the deadline passes. On Arc, settlement finalizes in under a second. No crew to email and no invoice to chase.
For Physical AI, that changes the question from "how long until we get data?" to "who is standing near the place right now?"
If your robot or agent needed a place it has never seen by Friday, which would you rather wait for: a crew, a unit, or a person with a phone?