The files that make UPS legible & callable to AI
Today any non-browser client to UPS gets a dropped connection or a 403 (Finding 1). This kit is the scaffold that opens a legible door: an llms.txt file (the file AI assistants read first) mapping capabilities, an A2A agent card and MCP tool schemas (the files that let an AI assistant use you correctly) for tracking-grade proof verification (one is a live x402 pay-per-use call), and a concierge persona, served on a path the bot wall permits, exactly like UPS's existing tracking APIs.
⚙ Prototype scaffold. Values drawn from UPS's public pages/reporting where available and markedTODO where UPS would confirm authoritative content. Nothing here is deployed; it's a starting point UPS would review and populate.
First-mover framing. We verified it: www.ups.com refuses non-browser clients (curl → 000) on every path and about.ups.com returns 403 to a browser-shaped fetch, so there's no agent surface even reachable today. UPS already publishes tracking APIs; an agent-legible discovery layer is the same idea, one layer up.
A plain-language map an assistant reads to answer "what can UPS do, and how do I verify an outcome", with a citation, not a scrape it can't even reach today.
# UPS: llms.txt (prototype, EcoWealth-authored concept) # Moving our world forward by delivering what matters, verifiably. > UPS provides global package delivery, freight, and supply-chain solutions, > with machine-verifiable proof-of-delivery at its core. ## What an agent can do here - Track a shipment / retrieve proof-of-delivery # via UPS's own tracking APIs, TODO confirm - Verify a settled sustainability/outcome receipt (Rolling-Lab mile, restore packet) - Discover EWP Restore packets at a hub or along a route ## Commitments an agent can cite - Carbon-neutral by 2050 (Scopes 1, 2, 3) - 40% alternative fuel + 25% renewable electricity targets # TODO UPS to confirm current status - Rolling Lab: 12,000+ low-emission / advanced-tech vehicles, 1M+ cleaner miles/day - Proof-of-outcome layer for the above: verify_outcome_receipt (below) ## Verify us - Agent identity + skills: /.well-known/agent-card.json - Proof-of-delivery (packages): existing UPS tracking / Complete View Signature - Outcome receipts (sustainability/worker commitments): verify_outcome_receipt - Live work-packet endpoint (standard x402, keyless): work_packet ($0.10) ## Boundaries - Public capabilities only. Account, shipping, and safety-sensitive operations route through UPS's authenticated systems, never an agent.
The machine-readable identity + skill list an assistant resolves before acting, currently unreachable behind the bot wall.
{
"protocolVersion": "0.3",
"name": "UPS: Capability & Verified-Outcome Concierge (concept)",
"description": "Answers public capability questions and verifies UPS outcome
receipts (sustainability, worker commitments, restore packets).",
"provider": { "organization": "United Parcel Service, Inc.", "url": "https://www.ups.com" },
"preferredTransport": "JSONRPC",
"capabilities": { "streaming": true },
"skills": [
{ "id": "get_capabilities", "description": "Services & commitments, with citations" },
{ "id": "verify_outcome_receipt", "description": "Replay a settled outcome receipt on-chain" },
{ "id": "find_restore_packet", "description": "EWP packets at a hub / along a route" }
],
"note": "Public capability agent only. No account, shipment, or safety-sensitive
action is taken here; those route to UPS's authenticated systems."
}
The callable surface. verify_outcome_receipt and work_packet are backed by EcoWealth's live rails on Base: the $0.10 x402 call in "The ask" runs against exactly this.
[
{ "name": "get_capabilities",
"description": "Return UPS services and commitments, with source citations.",
"input_schema": { "type":"object", "properties":{
"topic":{"type":"string"} } } },
{ "name": "work_packet", // live · standard x402 · $0.10 · keyless
"description": "Emit a bounded, funded work packet (scope, safety, proof reqs).",
"input_schema": { "type":"object", "required":["place","problem"],
"properties":{ "place":{"type":"string"}, "problem":{"type":"string"} } } },
{ "name": "verify_outcome_receipt",
"description": "Replay a settled outcome receipt: proof hashes, GPS, timestamps,
tCO2e, on-chain tx. The environmental analog of a POD signature.
Independent of UPS's internal systems. Fails closed.",
"input_schema": { "type":"object", "required":["receipt_id"],
"properties":{ "receipt_id":{"type":"string"} } },
"returns": { "verified":"boolean", "tco2e":"number", "tx":"string" } },
{ "name": "find_restore_packet",
"description": "Return open EWP Restore packets at a hub or along a route.",
"input_schema": { "type":"object", "required":["geo"],
"properties":{ "geo":{"type":"string"} } } }
]
Why this is the differentiator
The kit turns UPS's front door from "a dropped connection for any agent" into "capabilities an agent cites and outcomes a regulator verifies." It's a scaffold, built to be reviewed and populated by UPS: the honest first step under a 2050 pledge that currently has no machine-verifiable proof layer.
