Independent concept · Not affiliated with Southwest Gas · Unlisted
A leak survey is a work packet. So is every foot of it that a regulator asks you to prove.
Southwest Gas runs periodic leak surveys, a Customer-Owned Yard Line (COYL) replacement program, and integrity-management pipeline work across 2.28 million customers and 34,000+ miles of mains and service lines in Arizona, Nevada, and California. Every one of those tasks has the exact shape of a proof-verified work packet: bounded scope, a GPS location, photo proof, a signed sign-off, and PHMSA and the state commissions require the completion records to keep. This concept turns those records into permanent, machine-verifiable on-chain receipts. Live today.
Read this first. This is an independent, unsolicited concept demonstration by EcoWealth Corporation. It was not requested by, produced with, reviewed by, or endorsed by Southwest Gas Corporation, Southwest Gas Holdings, or any affiliate. Every observation comes from Southwest Gas's public web pages and public regulatory record only (passive reads, no scanning, no probing, no authentication). "Southwest Gas" is their mark, referenced descriptively. Every "demo" is a concept mock built on EcoWealth's own live data, no Southwest Gas data is used, and no adoption, partnership, or buyer relationship is claimed.
The whole thing, plainly
We found that Southwest Gas already does the field work regulators require proof of, leak surveys, yard-line replacements, but nothing on its public site lets anyone check that a specific job happened. We built a live, working way to turn that record into a permanent receipt, free to look at. The one ask: fund one packet, pocket change against the utility's own field budget.
Five facts from the public record
Field work = packet
Leak surveys + the COYL program are survey-a-location, find-a-defect, fix-it, document-it work: the exact shape EcoWealth already authors, proofs, and settles on-chain.
0 × ld+json
Zero structured data in the homepage or sustainability page. llms.txt (the file AI assistants read first), ai.txt, and every .well-known/ agent path are true 404s. No security.txt.
7,049 relative URLs
The sitemap ships 7,049 <loc> entries, all relative paths (/azbusrebate), which the sitemap protocol says must be absolute. A strict crawler can't resolve them.
$408M / yr
2024 utility capital for infrastructure modernization + integrity-management pipeline replacement, real, ongoing field work with mandatory completion records.
Report is a PDF
The 2024 Sustainability Report and RNG / methane commitments live as prose + PDF. Nothing on the site is an object an AI agent can verify.
The concept, in three pages
Capability brief
A field-work-first read of the public surface
Baseline credited first (the operations are real and regulated). Then five evidenced findings: the field-work/verification fit, the machine-illegible commitments, the relative-URL sitemap, the thin agent surface, and one security-hygiene note, each with the exact URL, HTTP status, and re-check command anyone can run.
Two acts in Southwest Gas's own palette and typeface: Act 1, a customer or agent asks "was the survey done at my address?" and today the answer is a PDF nobody can check. Act 2, the same task becomes a work packet with a bounded scope, photo+GPS+signature proof, and an on-chain settlement receipt any regulator, auditor, or customer can verify forever.
Concept files: an llms.txt that makes the safety, leak-report, and RNG surfaces discoverable, an A2A agent card, MCP tool schemas for verified field-work history, and a concierge persona. Drafts, ready to hand to their web team; EcoWealth runs the verification rail behind them.
Not slides, a running system: a work library with field lanes that already match utility work, civic_hazard_survey, ambient_air_survey, trenching_excavation_survey, confined_space_entry_survey, urban_canopy_survey, stormwater_inspection; 7,600+ live work postings / ~$671k posted value at capture (live counter: vealth.net/labor/stats, the counter is the truth, not this page); proof-checked packets (photo+GPS+signature); on-chain settlement on Base, EWP contract 0x76c17C…A14B, source-verified, first settled packet workId 14; agent-payable tools over standard x402 (work-packet $0.10 · work-proof-check $0.01 · work-tco2e $0.005); and a live end-to-end agent walkthrough: the building-agent golden path.
Put one agent on-chain today
The scary part, made small
Give any AI agent, Claude, a GPT-class model, Llama, your own, a Base wallet holding a few cents of USDC. No account with us, no API key, no sales call.
Point it at a live endpoint: the work-packet program answers HTTP 402 with a standard x402 payment schema (x402: a web-native way for AI agents to pay per use); the agent signs a USDC authorization and pays $0.10. A runnable client with a dry-run default is published at vealth.net/recipes.html.
What comes back is a bounded, proof-verified ecological work packet, and every step the agent just took (payment, settlement) is an on-chain receipt anyone can verify, forever.
Why this isn't scary: the agent cannot do anything invisible here. Every action embeds its own receipt: permanent, public, verifiable. That is more accountability than most enterprise software offers, not less. For a gas utility this is the regulatory-records argument in reverse: the completion records PHMSA and the ACC / PUCN / CPUC already require you to keep, produced automatically as you go.
The bet: AI competence is scaling, and your own industry is already there, advanced leak detection now runs on vehicle-mounted spectrometry (Picarro-class CRDS, ~1,000× more sensitive than hand-held) and AI-driven integrity management is standard vendor language across gas distribution. The one layer nobody has shipped is machine-verifiable proof the survey and the repair actually happened. Being early costs $0.10 and one afternoon. Being late means the proof-verified track records, of your own contractors, your own COYL replacements, your own desert right-of-way work, belong to whoever moves first.
Then: fund one packet, pocket change
For a utility that spent $408M on field infrastructure in one year, the first step costs less than a service call:
Fund one proof-verified field-adjacent packet in your own AZ / NV / CA territory, a desert right-of-way restoration or a leak-adjacent survey lane, for a two-figure dollar amount. The deliverable is a permanent on-chain proof receipt: place, time, photo, GPS, signature, settled.
Or have any AI agent make one x402 call against our live endpoint, work-packet at $0.10, and watch a bounded, safety-framed packet come back keyless.
Or a small bounded paid pilot: 10 packets across one district, each closed with proof and settled on-chain, a working answer to "prove the survey happened" you can put in front of a PHMSA auditor or the ACC / PUCN / CPUC.
Why you, specifically: your obligations already require the completion records. This just makes them independently verifiable instead of a PDF you have to be trusted on.
Most compliance is a document you're asked to trust. A receipt is a thing anyone can check. We sell the first brick: proof that the work at that address, on that day, actually happened.
