Shown, not told · two acts · one real, one concept
An AI agent can already retire carbon through your rail. Here's the one piece it still can't verify on its own.
Act One is real: the exact call shape EcoWealth's own agent uses today against Klima's Base infrastructure, with a transaction hash anyone can check independently. Act Two is a labeled concept: what finding 3's fix (in the brief) would look like on a retirement receipt, before and after.
Read this first. Act One narrates a real, previously-executed transaction, cited by hash, nothing is broadcast by loading this page. Act Two is a static, clearly labeled mockup, not a live page or a working prototype. Not requested by, produced with, reviewed by, or endorsed by Klima Protocol or KlimaDAO.
Act One: an agent retires carbon through Klima's rail, for real
Real transaction, cited by hash
This is the actual shape of the call, not a simulation. EcoWealth's own agent stack calls a tool named retire_and_certify; underneath, that tool calls the same Klima Base infrastructure this brief audits.
$ agent invokes retire_and_certifyagent>retire_and_certify({ amount_tco2e: 0.00005, beneficiary_name: "EcoWealth ecological work", retirement_message: "settled labor packet, Base mainnet EWP" })tool> returns the exact door to pay and call, keyless: no private key ever leaves the caller# underneath, the same call shape our production relay has used since July:relay>POST x402.klimalabs.com/api/actions/retire(EIP-712 signed, gasless)chain> Base mainnet, Retirement Aggregator, retireCreditViaKlima()tx> 0x96380e97f0f5c128b745448b47cfc77f036aa6daebf01383416497f179bad061status> confirmed, beneficiary correct in the retirement event log
ToolEcoWealth's live MCP tool retire_and_certify (schema in the Agent Kit)
Underlying railKlima's gasless relay, x402.klimalabs.com/api, settling to the Retirement Aggregator on Base
Real transaction0x9638...bad061 on BaseScan, independently re-checkable against Base's own RPC (eth_getTransactionReceipt)
Where it stands todayThe MCP tool and Klima's rail both still work; the automated cron that ran this on a schedule is paused by our own operator's order (2026-08-04), unrelated to anything in this brief
This already answers the "agent-payable" half of an AI-mediated retirement world: an agent with a wallet and this tool schema can retire real carbon on Base today, without a human clicking through a UI, and get back a transaction hash as proof. What it can't yet do is hand that transaction hash to a different agent and have that agent confirm, from Klima's own retirement page, what got retired, for whom, and how much, without also running a full browser. That's Act Two.
Act Two: what a self-proving retirement receipt would look like
Concept mockup, not a live page
Finding 3 in the brief: a real retirement URL and a fabricated one return byte-nearly-identical, generic page metadata. Here's the same receipt URL, today's link-preview card next to a concept of what it would show if the fix shipped.
Today · what any crawler or agent sees
klimaprotocol.com
Klima Protocol | Open Infrastructure for Carbon Markets
Open infrastructure for carbon markets. Klima Protocol enables transparency, instant execution, and traceable impact.
klimaprotocol.com/retirements/0x7e22.../1
Same card renders for a fabricated address and ID. No tonnage, no beneficiary, no date, no way to tell real from fake without running the app.
Concept · server-rendered before any JS runs
klimaprotocol.com
0.0500 tCO2e retired · Klima Protocol
Retired on Base mainnet, 2026-07-16. Beneficiary: EcoWealth ecological work. Tx 0x9638...bad061.
klimaprotocol.com/retirements/0x7e22.../1
Verifiable on-chain
A fabricated ID would 404 honestly at this same layer, before any client JS decides.
The concept JSON-LD behind the "after" card is in the Agent Kit, drafted in the same shape as EcoWealth's own verify_anchor tool: given a hash or an ID, say plainly whether it's real, and hand back the proof so the caller doesn't have to trust the page, they can check it themselves.
Put together, Act One and Act Two describe one loop: an agent retires carbon through Klima's rail (works today), and a second agent, or a human glancing at a shared link, verifies that retirement without running a full browser (the fix in finding 3 would close this). Neither half requires Klima to build anything EcoWealth hasn't already proven works on its own side of the interface.