What Google looks like when its surfaces answer agents

An agent finds Google's commitment, then routes a human to real, verified work.

Two changes, both shown here. First: the agent-facing well-known file that's a 404 today becomes a real agent card. Second: a Gemini-style agent uses it to route a person into a funded, proof-verified Restore work-packet that settles on-chain. Palette drawn from Google's own; every panel is concept, tuned to WCAG AA.

Concept demonstration · not a Google product · illustrative endpoints

The one file that changes everything: today vs. concept

GET /.well-known/agent-card.json, today

$ curl -s -o /dev/null -w "%{http_code}"
    https://www.google.com/.well-known/agent-card.json
404   # captured 2026-07-14

# an A2A agent asks "what can this surface do?"
# and gets an HTML error page.

GET /.well-known/agent-card.json, concept

{
  "name": "Google Sustainability Agent",
  "protocol": "a2a/1.0",
  "skills": [
    "query_carbon_commitment",
    "discover_ecological_work",
    "route_to_ewp"
  ],
  "partners": ["vealth.net"]
}

Left panel is real (reproduce the 404 yourself). Right panel is the concept file that would make the surface legible over A2A, Google's own donated standard.

The demo: press play

Gemini-style assistant A2A · x402

A person asks an assistant for real climate work, and to prove it happened.

The agent card is two files. The destination is already on-chain.

Google standardized how agents discover and pay each other. This is what it looks like when Google's own surfaces answer, and hand the person a funded, proof-verified place to do the work. See the exact files next.

Open the Agent Kit →