Passive, reproducible recon · four findings · 2026-07-14
This is an honest read of UPS's public surface as any customer, regulator, union rep, or AI agent encounters it, gathered passively, no probing, no authentication. It credits a genuinely strong baseline first, then names four opportunities that trace to one primitive UPS already sells and EcoWealth builds: machine-verifiable, tamper-evident proof of work done at a place. Under the ruthless-evidence bar, each finding leads with a command + the exact result.
UPS's entire brand rests on a primitive EcoWealth also builds: machine-verifiable chain-of-custody. Signature Required and Complete View® Signature give any customer independently-checkable proof-of-delivery: time, address, and the signature of who accepted it. Email authentication is fully enforced: _dmarc.ups.com is p=reject and SPF ends -all (hardfail), via Proofpoint. And the Rolling Lab, 12,000+ low-emission/advanced-technology vehicles logging 1M+ cleaner miles/day, is real operational substance, not a slogan. UPS knows how to make proof machine-verifiable; the findings below are about pointing that same rigor at its own front door and its own commitments.
No jargon: what each finding below is worth to UPS in plain terms.
A non-browser client is dropped at the edge today, so an assistant asked to represent UPS gets nothing; a static profile on a permitted path lets it answer accurately.
A settled, tamper-evident outcome object turns "trust the report" into "verify it," exactly like the signature UPS built its brand on.
Each delivered or retrofitted vehicle becomes a receipt both sides trust, so progress settles on evidence instead of in grievance, a de-escalation tool, not a fight.
The findings
What an agent hits
Not a 404 for a missing file: a refusal to connect. Any non-browser client to www.ups.com gets a dropped connection (curl → 000) on every path, including robots.txt and sitemap.xml. about.ups.com returns 403 to a browser-shaped fetch.
Why it matters
The AI-commerce and RFP-answering wave reads a company through agent clients. A wall that hard means UPS is categorically invisible to that layer, and there's no llms.txt or agent card even reachable to fix it.
The precise, reproducible state: a non-browser TLS client to www.ups.com is dropped at the edge: curl returns exit-status 000 (no HTTP response) across the homepage and every well-known path we tried. about.ups.com answers a browser-shaped fetch with 403 Forbidden. So unlike Uber (404/406) or ABM (a real 200 llms.txt), UPS's agent-discovery state can't even be probed by a normal client, the block is total. The honest framing: we report the block itself as the finding, not an inferred "404."
$ for p in "" llms.txt robots.txt sitemap.xml .well-known/agent-card.json; do \
curl -s -o /dev/null --max-time 25 -w "www.ups.com/$p -> %{http_code}\n" https://www.ups.com/$p; done
www.ups.com/ -> 000 # connection reset / refused, no HTTP response
www.ups.com/llms.txt -> 000
www.ups.com/robots.txt -> 000 # even robots.txt is unreachable to a non-browser
www.ups.com/sitemap.xml -> 000
www.ups.com/.well-known/agent-card.json -> 000
# about.ups.com (sustainability pages live here), browser-shaped fetch:
GET https://about.ups.com/us/en/our-impact/sustainability/... -> 403 Forbidden
# contrast: UPS CAN do strict machine policy; it just hasn't extended it to agents:
$ dig +short TXT _dmarc.ups.com
"v=DMARC1; p=reject; …@emaildefense.proofpoint.com; fo=1" # enforced
The fix EcoWealth brings: a static, agent-legible discovery layer, llms.txt + agent card + MCP tools, served on a path the bot wall permits (the way UPS already exposes tracking APIs), so an assistant can represent UPS accurately instead of hitting a wall. Drafted in the Agent Kit.
This is the sharpest fit. UPS's product is proof: Complete View® Signature lets a customer independently verify a delivery happened: time, place, signature. Yet UPS's own sustainability commitments, carbon-neutral by 2050 (Scopes 1, 2, 3), 40% alternative fuel + 25% renewable electricity targets, the 12,000+ vehicle Rolling Lab, are published as reports and PDFs on about.ups.com (which 403s agents), with no machine-verifiable proof-of-outcome object. The company that made "you can verify the delivery" a global standard asks the public to take its own environmental progress on trust.
Today
"Is UPS on track for its 2050 pledge? Was this a Rolling-Lab mile?" → a report to trust, behind a 403 wall for agents.
With a proof layer
A settled, tamper-evident receipt, per Rolling-Lab mile, per facility restore packet, a regulator or customer replays independently, exactly like a POD signature.
Why EcoWealth fits: our primitive is a proof-verified, on-chain-settled, tCO2e-mapped outcome receipt: the environmental analog of the signature UPS already trusts. It turns "we pledge" into "here's the receipt." Shown in the demo.
Strip a delivery to its mechanics: a worker is dispatched a bounded task (a stop), directed to a place, proves completion (scan + GPS + signature/photo), and it settles into the tracking record. That is, line for line, an EcoWealth work packet. Across ~490,000 employees and one of the largest agent-dispatched task networks on earth (ORION route optimization), UPS already runs the exact behavior EWP needs, millions of times daily. EWP adds three things: the proof is public and verifiable (not internal to tracking), settlement is on-chain, and the task can be a Restore packet, at a UPS hub, or at a facility along an existing route.
Why the geography fits
A route is already a proven sequence of places. A restore packet is a bounded, mapped stop, the same dispatch-prove-settle loop, pointed at a place worth restoring.
Why it's low-friction
No new behavior to teach a workforce that scans+signs+GPS-stamps all day, and no new dispatch primitive for an ORION-class network.
This finding rides on Findings 1–2: the pattern-fit only pays off once there's an agent-legible door (F1) and a verifiable outcome object (F2). Together they make UPS's own network an on-ramp to proof-verified ecological work.
UPS's national master agreement is the largest private-sector collective-bargaining agreement in North America. It included a commitment to add 28,000 air-conditioned delivery vehicles. As publicly reported by the Teamsters, roughly 10% had been delivered, a dispute that turns, precisely, on proof of progress both sides trust. We carry this as an attributed public claim, not our own audit; the load-bearing point holds regardless of the exact percentage: a commitment to workers with no independent, machine-verifiable progress record is the same shape of gap as a sustainability pledge without a receipt.
Today
Progress on a worker commitment is asserted by one side and doubted by the other, it settles in grievance, not on shared evidence.
With a proof layer
Each delivered/retrofitted vehicle → a tamper-evident receipt on a ledger both UPS and the union read the same way. Trust by verification, not assertion.
Framed as opportunity, not attack: UPS already trusts the signature between itself and its customers. The same primitive, applied to a commitment between UPS and its workforce, is a de-escalation tool: a shared, verifiable record that makes "we're on track" checkable by everyone.
Evidence log: every claim, re-runnable
| # | Claim | Reproduction command | Result observed 2026-07-14 |
|---|---|---|---|
| 1 | www.ups.com refuses non-browser clients on every path | for p in "" llms.txt robots.txt sitemap.xml; do curl -s -o /dev/null --max-time 25 -w "$p %{http_code}\n" https://www.ups.com/$p; done | all 000 (connection reset / no HTTP response) |
| 1 | about.ups.com 403 to a browser-shaped fetch | browser-shaped GET of an about.ups.com sustainability page | 403 Forbidden |
| base/1 | Email auth enforced: DMARC p=reject, SPF -all | dig +short TXT _dmarc.ups.com ; dig +short TXT ups.com | p=reject; fo=1 (Proofpoint) ; SPF ends -all |
| 2 | Carbon-neutral 2050; 40% alt-fuel + 25% renewable-electricity targets; 12,000+ Rolling-Lab vehicles, 1M+ cleaner miles/day, report/PDF, no proof object | Public reporting + about.ups.com sustainability pages (403 to agents) | Commitments confirmed; no machine-verifiable outcome layer |
| 3 | ~490,000 employees (254,360 FT + 235,640 PT, Dec 31 2025); ORION route network; POD = scan+GPS+signature | Public reporting (MacroTrends / UPS filings) + ups.com POD product pages | Confirmed order-of-magnitude |
| 4 | National master agreement (largest private-sector CBA in N. America); 28,000 A/C vehicles committed, ~10% delivered per Teamsters | Public reporting, attributed to the Teamsters (secondary source), not our audit | Reported figure; carried as attributed claim |
A logistics business is proof end to end. UPS made that machine-verifiable for packages; the opportunity is to point it at its own commitments.
Enterprise + SMB shipping on reliability + verifiable delivery. Complete View Signature is a paid, machine-verifiable proof product, proof already sells for UPS.
EWP plug: the same proof, on its own outcomes~490k workers on an ORION-optimized, agent-dispatched network; every stop captured as scan+GPS+signature, internal to tracking.
EWP plug: public, on-chain proof receipts (F3)Trust, with customers (POD), regulators (ESG), and workers (the CBA). Each rests on proof one side must accept.
EWP plug: shared, verifiable ledgers (F2, F4)An estate that 000/403-blocks agents is invisible to AI commerce + RFP tooling, while peers begin publishing agent surfaces.
EWP plug: the Agent Kit (F1)Today
With the Kit + Protocol
Not "let's talk." One bounded first step, a rounding error against UPS's scale, that returns a verifiable receipt tied to carbon-neutral 2050, held to the same standard as the signature UPS built its brand on.
Point any UPS agent at our live work-packet endpoint (standard x402, keyless). It returns a real work-packet object, the agent-legible door your estate currently 000/403-blocks, working in one call.
Fund one restore packet at a UPS hub or along a route; completion is scan-style photo+GPS+signature and it settles on-chain as a receipt a regulator verifies. The deliverable is the receipt.
One hub, proof-verified Rolling-Lab-mile or restore receipts → a tamper-evident progress ledger citable under carbon-neutral 2050. Fixed, reversible, proof before scale.
Why now: your 2050 commitment is a report to trust (F2). Each option ends in a receipt anyone verifies themselves, the standard UPS already sells to its own customers.
The through-line
The findings compound: an agent-legible door on an estate that blocks agents (F1), the signature-grade proof UPS sells applied to its own commitments (F2), the route network already running the pattern (F3), and a shared, verifiable ledger for a worker commitment (F4).
