Exomad Green is already agent-ready, rare among everything we've reviewed. That's the headline, not a footnote.
In one plain sentence: Exomad Green is a Bolivia-based biochar producer claiming the largest CDR (carbon dioxide removal) delivery volume in the industry (1.4Mt removed to date, ~24.5% of all durable removals), and, unusually among the verification-orbit entities we've reviewed, it ships a real, working AI-agent integration (a live Wix MCP endpoint: MCP is the protocol that lets an AI assistant call a site's tools directly) rather than just a static file, which this page credits first.
Relationship, stated plainlyEcoWealth has no relationship of any kind with Exomad Green: no contract, no integration, no contact, nothing sent. Independent, unsolicited, passive desk research, staged locally and not shared anywhere.
Read this first. Independent recon by EcoWealth Corporation. Not requested, produced, reviewed, or endorsed by Exomad Green. Public pages only, no scanning, no fuzzing, no sign-up, no contact. Captured 2026-07-16, all URLs independently re-runnable.
The whole thing, plainlyWhat we found: Exomad Green is a real, megatonne-scale biochar producer with a working AI-agent integration (a live Wix MCP endpoint), the only target we've reviewed that's already agent-ready. What we built: nothing to install; this is a courtesy technical note, free to read either way. What we're asking: nothing, no partnership pitch, no contact made, no meeting requested.
5 facts from the public record
Credit-first, because real credit is due. Each fact is reproducible; the brief has the exact source quote and re-check command.
A working agent-integration surface, rare
A real llms.txt (the file AI assistants read first: 200, 3,395B) documents a live Wix MCP endpoint (/_api/mcp) with named callable tools; robots.txt (the file that tells search engines what to index) explicitly Allows PerplexityBot, Google-Extended, CCBot, OAI-SearchBot, ChatGPT-User.
Two operating plants, real scale
Concepción (7 lines, 140,000 t CO2/yr, Sylvera AA) + Riberalta (6 lines, 120,000 t CO2/yr, Sylvera + BeZero AA); Guarayos under construction.
1.4Mt CO2 removed to date
~24.5% of all durable carbon removals industry-wide by Exomad's own claim; 108,000 t biochar/yr produced, 400+ green jobs created (2025).
The Microsoft megadeal
A 10-year, 1.24-million-tonne biochar offtake with Microsoft, tracked by Carbonfuture MRV+, the industry's first megatonne biochar deal (from EcoWealth's earlier public research).
2027 targets
5 facilities, 1,000,000 t CO2/yr, 400,000+ t biochar/yr, 1,500+ green jobs.
The brief
Capability brief
Four evidenced findings, credit-first
Exomad's real agent-integration surface (the standout finding), its production scale across two plants, the Microsoft megadeal, and its role as the raw producer at the base of the verification stack.
Exomad Green is a producer: the honest EWP angle here is provable field labor around the production sites themselves: feedstock collection and hauling at Concepción/Riberalta/Guarayos, farmer biochar-distribution days (Exomad donates biochar free to indigenous communities and farmers), and site-prep labor for the new Guarayos line. None of this claims carbon-credit eligibility; it's a receipts layer under work that already happens, never a substitute for Sylvera/BeZero ratings or Carbonfuture's dMRV. One extra, low-effort observation worth naming: because Exomad already runs a live Wix MCP endpoint, an EWP-side agent could technically query Exomad's own public site data (via SearchInSite/GetBusinessDetails) today, with no integration work on either side, a genuine "agent can already talk to them" fact, not a proposal.
What this hub asks for, and what it doesn't
Not a partnership pitch, not a sales ask. No one at Exomad Green knows this package exists. It is a courtesy-grade technical note prepared entirely from public information.
What it explicitly is not: a claim that EWP packets are carbon-credit-eligible, a claim of any integration or affiliation, or a request for a meeting.
The honest smallest next step, if ever raised: none proposed as a build, this is a pure observation package; if ever raised, the smallest step would be drafting sample EWP work definitions for feedstock-collection/site-prep labor at a named plant, with no contact required first.
Exomad didn't ship a static file and call it agent-ready, it shipped a working agent-integration endpoint. That's the one credit across everything we've reviewed that flips the usual finding: for once, the gap is on our side, not theirs.
