EcoWealth×Uber Agent Kit · prototype

The files that make Uber legible & callable to AI

The four files Finding 1 says are missing, drafted, so any assistant can represent Uber and act on a verifiable packet.

Today an agent asked about Uber's public surface gets a 404/406 (Finding 1). This kit is the static, verifiable 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, including a live x402 pay-per-use work-packet call), and a concierge persona that knows when to route to a human.

⚙ Prototype scaffold. Values are drawn from Uber's public pages where available and marked TODO where Uber would confirm authoritative content. Nothing here is deployed; it's a starting point Uber would review and populate.

First-mover framing. We verified it: www.uber.com/llms.txt is a 404 and /.well-known/agent-card.json is 406-blocked at the edge today. Uber already champions agent identity publicly: publishing the static door is the natural completion of that story, not remediation.

1

llms.txt

/llms.txt

A plain-language map an assistant reads to answer "what can I do with Uber, and how do I verify an outcome", with a citation, not a guess.

# Uber: llms.txt (prototype, EcoWealth-authored concept)
# Move people, things, and now verifiable ecological work.

> Uber operates a global real-time marketplace: rides, delivery (Uber Eats),
> freight, and, in this concept, proof-verified Restore work packets.

## What an agent can do here
- Estimate and (with user auth) request a ride or delivery  # via Uber's own APIs, TODO confirm
- Discover nearby EWP Restore packets claimable between rides
- Verify a settled work/outcome receipt (independent of any one platform)

## Commitments an agent can cite
- Zero-emission platform by 2040; 100% EV rides US/CA/EU cities by 2030
- Green Future driver EV-transition program (~$800M)  # TODO Uber to confirm current figures
- Proof-of-outcome layer for the above: see verify_receipt (below)

## Verify us
- Agent identity + skills: /.well-known/agent-card.json
- Outcome receipts (green trips / restore packets): verify_receipt (MCP)
- Live packet endpoint (standard x402, keyless): work_packet ($0.10)

## Boundaries
- This file describes public capabilities only. Account actions, pricing,
  and safety-sensitive operations route through Uber's authenticated systems.
2

A2A Agent Card

/.well-known/agent-card.json

The machine-readable identity + skill list an assistant resolves before acting: the exact path that returns 406 today.

{
  "protocolVersion": "0.3",
  "name": "Uber: Capability & Verified-Work Concierge (concept)",
  "description": "Answers public capability questions and verifies outcome
                  receipts for green trips and ecological Restore packets.",
  "provider": { "organization": "Uber Technologies, Inc.", "url": "https://www.uber.com" },
  "preferredTransport": "JSONRPC",
  "capabilities": { "streaming": true },
  "skills": [
    { "id": "get_capabilities", "description": "Services & commitments, with citations" },
    { "id": "find_restore_packet", "description": "Nearby EWP packets by geography" },
    { "id": "verify_receipt", "description": "Replay a settled outcome receipt on-chain" }
  ],
  "note": "Public capability agent only. No account, payment, or safety-sensitive
          action is taken here; those route to Uber's authenticated systems."
}
3

MCP Tool Schemas

agent/tools.json

The callable surface. verify_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": "find_restore_packet",
    "description": "Return open EWP Restore packets near a city geography.",
    "input_schema": { "type":"object", "required":["geo"],
      "properties":{ "geo":{"type":"string"}, "max_minutes":{"type":"integer"} } } },

  { "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_receipt",
    "description": "Replay a settled receipt: proof hashes, GPS, tCO2e, on-chain tx.
                    Independent of any single platform. Fails closed.",
    "input_schema": { "type":"object", "required":["receipt_id"],
      "properties":{ "receipt_id":{"type":"string"} } },
    "returns": { "verified":"boolean", "tco2e":"number", "tx":"string" } }
]

4 · Concierge persona: how the agent behaves

  • Accurate or silent. Answers only from Uber's confirmed public data with a citation. Unknown fact → says so and routes to a human; never invents a figure or a commitment.
  • Never acts on the account. Pricing, ride requests, payments, and safety-sensitive operations route to Uber's authenticated systems: this agent discovers and verifies, it does not transact on someone's behalf.
  • Verification is the superpower. Shown a receipt, it replays the proof on-chain and reports verified / not-verifiable plainly. No valid receipt, no claim.
  • Discloses itself. Identifies as a concept capability assistant (prototype), not a person, not an official Uber product.

Why this is the differentiator

No web vendor ships this. It's the static, verifiable door the "Uber AI Solutions" story already implies.

The kit turns Uber's front door from "prose an AI must scrape (404/406 today)" into "capabilities an agent cites and outcomes an auditor verifies." It's a scaffold, built to be reviewed and populated by Uber: the honest first step under a 2040 pledge that currently has no machine-verifiable proof layer.

Provisioned by EcoWealth · Digital Provisioning Protocol · provenance‑sealed