EcoWealth×Apple Capability Brief · evidence-led

Five findings · every one independently reproducible

A world-class climate program, provable only once a year, on paper.

This brief leads with evidence. Apple's own pages establish the funded substance; a soft-404-controlled HTTP sweep establishes the agent-discovery gap; and the same sweep shows Apple already ships maintained, machine-readable well-known files, so the missing piece is small and in-character. The EcoWealth positioning rides on the proof.

Method: passive only. Plain curl GETs of standard public paths (/llms.txt, /ai.txt, /robots.txt, /.well-known/*) plus a soft-404 control path to prove 404s are real. WebSearch / WebFetch for Apple's own published figures, quoted with source URLs. No authentication, no scanning, no probing. Captured 2026-07-14.

The bottom line, in plain English

Give the Restore Fund a receipt anyone can check → a live, continuously-auditable ledger instead of a once-a-year PDF

Your climate program is world-class, but its proof arrives once a year on paper — a per-project on-chain receipt answers the skeptical regulator, auditor, or customer continuously, turning an annual attestation into something they can verify the day they ask.

Make the environment story answerable by an assistant → you keep the customer whose question you can't answer today

When someone asks their assistant “how green is this iPhone?” there's nothing structured for it to read, so the answer they act on isn't yours — a small agent surface means your real, accurate environment story reaches the customer already asking.

Expose trade-in, repair, and product-environment data cleanly → the accurate answer and the transaction come from Apple, not a scraper

As assistants start shopping on people's behalf, being the company whose trade-in quote and environmental sheet an AI can read straight from you protects the brand and captures the sale — and France's AGEC sheet shows this data is coming regardless.

You already maintain machine-readable files → the agent ones are the same small, in-character step

Apple already ships and maintains structured well-known files for security and app-linking, so adding the agent-facing ones isn't new muscle — it's the identical maintained-file work, one step from making the whole story legible to the assistants customers use.

Finding 1: The commitment is credible and funded. The proof is a PDF.

Substance · credited
Apple's own numbers, and where they live

Apple 2030 and the Restore Fund are real. An agent still can't verify a single project.

What we observed

Apple 2030 is Apple's ambitious, science-based goal to become carbon neutral across our global footprint, a 75% cut vs 2015, balancing the rest. The Restore Fund began as a first-ever $200M fund (2021, with Conservation International & Goldman Sachs, aiming to remove ≥1M metric tons CO₂/yr), grew by another $200M in 2023 (Climate Asset Management), and expanded again in 2025 (US + Latin America). The Supplier Clean Energy Program generated more than 38 million megawatt-hours in 2025. This is among the most credible corporate climate programs on earth, and its proof is published as the annual 2026 Environmental Progress Report PDF, attested once a year, not as per-project objects anyone can verify continuously.

Proof (sources)

# quoted verbatim from Apple's own pages
open https://www.apple.com/environment/
open https://www.apple.com/newsroom/2021/04/apple-and-partners-launch-first-ever-200-million-restore-fund/
# the 2026 Environmental Progress Report is offered as a PDF download

Why it matters to Apple

An annual attestation answers "did Apple hit its target?" once. A per-project, on-chain outcome receipt answers "is this specific restoration real, and by how much?" continuously: the difference between a report and a live ledger, and exactly what a skeptical regulator, auditor, or customer increasingly wants.

Finding 2: No agent surface on apple.com

Agent-discovery gap
Reproducible HTTP capture (2026-07-14)

The environment story can't be discovered or acted on by an assistant.

PathStatusRead
www.apple.com/llms.txt404No LLM index
www.apple.com/ai.txt404No AI-usage file
www.apple.com/.well-known/agent-card.json404No A2A (a protocol that lets AI agents discover and call each other) agent card
www.apple.com/.well-known/ai-plugin.json404No plugin manifest
www.apple.com/…/soft404-control404Control: 404s are real
developer.apple.com/llms.txt404Dev portal: no LLM index

Proof (reproduce it)

curl -s -o /dev/null -w "%{http_code}\n" https://www.apple.com/llms.txt # → 404
curl -s -o /dev/null -w "%{http_code}\n" https://www.apple.com/.well-known/agent-card.json # → 404
curl -s -o /dev/null -w "%{http_code}\n" https://www.apple.com/this-is-a-soft404-control-xyz123.txt # → 404 (control)

Why it matters to Apple

When a customer asks an assistant "how green is this iPhone?" or "what's my trade-in worth?", there's no structured surface for it to read. A small agent surface makes Apple's environment story answerable, accurately, by the assistants customers already use.

Finding 3, credit where due: Apple already ships machine-readable well-known files

Baseline credited
The habit is there; the agent files aren't

Apple maintains structured well-knowns, just not the agent-facing ones.

What we observed

apple.com/.well-known/security.txt returns HTTP 200 (a real, maintained file: Apple Security Bounty policy, Expires 2027-06-21), apple.com/.well-known/apple-app-site-association returns 200 (application/octet-stream), and robots.txt lists multiple maintained sitemaps (shop, newsroom, retail, today). Apple plainly values and maintains machine-readable well-known files. The agent-facing ones (llms.txt, agent-card.json) are simply not among them yet.

Proof (reproduce it)

curl -s -o /dev/null -w "%{http_code} %{content_type}\n" https://www.apple.com/.well-known/security.txt # → 200 text/plain
curl -s -o /dev/null -w "%{http_code}\n" https://www.apple.com/.well-known/apple-app-site-association # → 200
curl -s https://www.apple.com/robots.txt | grep -i sitemap

Why it matters to Apple

Same honest frame as every strong operator: adding an llms.txt and an agent-card.json is the exact class of maintained-file work Apple already does for security and app-linking. The lift is minimal, and it fits how Apple already builds.

Finding 4: The commerce surface isn't agent-readable either

Commerce legibility gap
Trade-in · repair · environmental sheet

An assistant can't quote a trade-in value or fetch a product's environmental sheet.

What we observed

Apple runs genuinely strong circular-economy programs: Apple Trade In (free recycling / credit), Self Service Repair (genuine parts, tools and manuals in the US and parts of Europe), and refurbished. But their data (a trade-in quote, a repair-part price, a product's environmental characteristics) isn't exposed as structured, agent-readable objects. Notably, France's AGEC circular-economy law already requires Apple to publish a per-product environmental sheet, which Apple does, a regulatory precedent that per-product, machine-readable environmental data is coming regardless.

Proof (sources)

open https://support.apple.com/self-service-repair # genuine parts + manuals
open https://www.apple.com/environment/answers/ # per-product environmental data (AGEC)

Why it matters to Apple

Agent-driven commerce is arriving. Being the company whose product, trade-in and environmental data an assistant can read accurately (sourced from Apple, not scraped) protects the brand and captures the transaction. The AGEC sheet is the on-ramp; the Agent Kit shows the pattern.

Finding 5: The Restore Fund is EWP's home turf, as per-project proof

Where EcoWealth plugs in
Riding on the proof above

Each restoration becomes a funded, verified, settled object, not a line in a report.

What we observed

The Restore Fund invests in forestry and ecosystem restoration that generates carbon removal. EWP is a funded, proof-verified work layer whose Restore ladder is exactly that subject matter: each project scoped as a work-packet, funded before the work, proof-verified (photo + GPS + method), and settled on Base mainnet with a tCO2e receipt. It doesn't replace Apple's audited report. It makes each project a live, public, per-project object the report can point to.

The destination (all reproducible)

# EWP is live on Base mainnet, source-verified
open https://basescan.org/address/0x76c17C51336BE7B39F5164802e08b9811477A14B
curl -s https://vealth.net/labor/stats # live board
curl -s https://vealth.net/.well-known/x402 # machine payment lanes

Why it matters to Apple

Reachable keyless over x402 (a web-native way for AI agents to pay per use: work-packet $0.10, plus proof-check / tCO2e / method-template / settlement-attest); first fully settled packet on-chain workId 14, 2026-07-07. It gives the Restore Fund a continuously-auditable per-project proof layer that complements the annual attestation.

Where the Work Protocol plugs into Apple

Three competence ladders, step-one-anyone-today to mastery: every job funded, proof-verified (photo + GPS + method), settled on Base with a tCO2e receipt. The Restore Fund funds the work; EWP settles each project into a verifiable object.

Build · LBC

Living Building Challenge: regenerative construction for Apple's facilities & supplier sites.

Grow & Cook · Michelin

Regenerative food & land work: a ladder for supplier-community programs.

Restore · UN SDGs

Ecological restoration mapped to tCO2e: the Restore Fund's projects, made per-project verifiable.

Give the Restore Fund a receipt anyone can check, without changing a thing you already do.

Apple runs one of the most credible climate programs in the world and already ships maintained machine-readable files. Attaching per-project on-chain proof is small, in-character work that turns an annual attestation into a live ledger. The destination is running.

See it running →

The ask: proof first, then a small yes

One dime proves it. One funded packet makes the Restore Fund auditable in real time.

Proof first, ask second. The deliverable is always an on-chain receipt, never a vague "let's talk."

$0.10 · today
Point any agent at our live x402 endpoint. One keyless call returns a real, signed work-packet: the whole proof, for a dime, no Apple system touched.curl https://vealth.net/.well-known/x402
Fund one packet
Back a single proof-verified Restore packet in a Restore Fund region. A rounding error against a $200M+ fund. Deliverable: an on-chain tCO2e receipt that complements the annual report with a continuously-auditable per-project object.
Bounded pilot
An agent-readable environmental-sheet endpoint for one product line, plus one on-chain Restore packet. Small, scoped, entirely on EcoWealth infrastructure.
Fund one packet · [email protected]
Provisioned by EcoWealth · Digital Provisioning Protocol · provenance‑sealed