EcoWealth is a live integrator, not a cold read: our carbon-retirement path calls v0.x402.klimalabs.com/api (x402 = a web-native way for AI agents to pay per use) and the Retirement Aggregator on Base, gasless and keyless. It ran twice daily until retirements are stopped by operator order as of 2026-08-04. Klima Protocol and Carbonmark have built one of the most agent-documented stacks we've reviewed, real llms.txt files (the file AI assistants read first), full GitBook markdown exports, a real OpenAPI spec, even a published Claude-Code skill plugin. This is the evidenced note on where that surface is genuinely strong, where a soft-200 quietly tells an agent something exists when it doesn't, and the one worked example, already running in production, of the agent-native demand carbon.fyi says it's trying to serve.
Klima's docs for AI agents are some of the best we've seen, but a few of the file paths an agent checks first quietly say "yes" when the answer is really "no."
We already retire carbon through Klima's real rail every day, so we drafted the three small fixes for free. The only ask: a technical look from Klima's own team, not a meeting.
New: the whole build, walked as one runnable sequence: Regenerative finance you can run →
noindex, and not sent anywhere without explicit review.Credit-first, because the credit is real. Each fact is reproducible with one command, the brief has the exact curl lines and HTTP statuses.
llms.txt on both marketing sites, full GitBook llms-full.txt exports (78–80 KB each), a real 84 KB OpenAPI spec, and a published Claude-Code skill plugin on GitHub.agent-card.json, ai-plugin.json, security.txt, .well-known/x402, returns the SAME bytes as a nonsense-path control. Looks like success; isn't.app.klimaprotocol.com, where a human actually retires, true-404s every agent path, real or fake..well-known/x402 on the branded endpoint is a clean 404. The live shape is a good, bespoke GET API, just not the open convention its name implies.Six evidenced findings: the credit, the soft-200 desert, the app-domain true-404s, the x402-naming gap, carbon.fyi's missing feed, and the live worked example, each with the exact URL, status, and re-check command. Plus one internal note we owe ourselves (a deprecated API version in our own legacy fallback path).
Read the briefIn Klima's own palette: a settled EWP work packet's footprint discovered, quoted, and retired through the gasless relay, resolving to a public Carbonmark certificate, the exact flow Carbonmark's own llms.txt describes wanting. Then the one standards layer that would let ANY agent do this without reading our code first.
Run the demoConcept files: a real .well-known/x402 manifest, an A2A agent-card.json, MCP (the protocol that lets an AI assistant call your tools) tool schemas matching the four-step discover/quote/prepare/retire flow Klima already documents, and a concierge persona. Built to sit on top of what Klima already ships, not replace it.
0x76c17C…A14B settles real-world ecological labor on Base mainnet; a share of settled work retires carbon through Klima's gasless relay (v0.x402.klimalabs.com/api, quote → prepare-auth → EIP-712 sign → actions/retire, hard $0.25 micro-cap) and directly through the Retirement Aggregator (retireCreditViaKlima, 0xda0a793d…4f4) on an twice-daily, gas-gated cron. Every retirement resolves to a public Carbonmark certificate, exactly what Carbonmark's own llms.txt says the x402 endpoint is for.
We entered, with the service, not a slide. Retire-attach: retirement as a service: any agent pays $0.25 through a standard x402 payment and this machine executes a real, attributed retirement through Klima's Retirement Aggregator. One payment is the entire integration: no keys, no slippage handling, no beneficiary plumbing on the caller's side. It was live and revenue-positive before the window opened.
Scored in the window: a named in-window paid retirement on July 18 (tx →), and the twice-daily gas-gated machine retiring through Klima's own hosted relay for the rest of the window (resumed after riding out Klima's mid-window facilitator-v2 API migration in production: first resumed tx →).
Why this entry is this page in miniature: everything documented here, the gasless relay, the aggregator path, the twice-daily habit, the public ledger, the 60-second verification, is what the entry sells. The body of work is the submission. The entry page →
Not a partnership pitch, not a sales ask. Two small, technical, in-character additions, one page each, matching a pattern you've already shipped elsewhere in your own stack.
/.well-known/agent-card.json and /.well-known/security.txt either real files or real 404s on both marketing domains, the current soft-200/soft-400 tells agents something exists that doesn't.x402.klimalabs.com/.well-known/x402 is exactly where a generic x402-aware client looks first, right now it 404s even though the endpoint behind it works great once you already know its shape.What we're not asking: no partnership announcement, no co-marketing, no change to the retirement mechanics we already depend on working exactly as they do today. This is a technical note from one node in your agent graph to the team that built the rest of it.
