What Apple looks like when its environment surface answers agents

An agent reads the environmental sheet, then verifies the restoration on-chain.

Two changes, both shown here. First: the agent-facing well-known file that's a 404 today becomes a real agent card. Second: an assistant reads a product's environmental sheet as structured data, verifies a Restore project's on-chain outcome receipt, and funds the next Restore packet over x402. Palette drawn from Apple's own; every panel is concept, tuned to WCAG AA.

Concept demonstration · not an Apple 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.apple.com/.well-known/agent-card.json
404   # captured 2026-07-14

# an assistant asks "what can this surface do?"
# and gets an error page.

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

{
  "name": "Apple Environment Agent",
  "protocol": "a2a/1.0",
  "skills": [
    "get_product_environment",
    "get_restore_project",
    "fund_restore_packet"
  ],
  "partners": ["vealth.net"]
}

Left panel is real (reproduce the 404 yourself). Right panel is the concept file that makes Apple's environment surface legible over A2A, the same class of well-known file Apple already ships for security and app-linking.

The demo: press play

On-device assistant A2A · x402

A customer wants to know a product's footprint and back a real restoration.

The agent card is two files. The Restore proof is already on-chain.

This is what it looks like when Apple's environment surface answers, and hands the customer a per-project restoration they can verify and fund. Nothing touches Apple's systems. See the exact files next.

Open the Agent Kit →