Plain thesis: Microsoft's carbon removal program is the biggest we've reviewed anywhere, and it runs entirely outside the Frontier coalition it's often assumed to belong to. This brief is credit-first: where Microsoft is genuinely ahead, it says so, then names the one machine-readability gap and the one honest complement EWP could offer, each with the command to verify it yourself.
No jargon. Microsoft's removal program is the largest we've reviewed and credited in full; the fixes below are about the one gap this review found: a domain external agents can't read. Here is what each one is worth.
microsoft.com returns a true 404 to every agent-discovery path, so an AI (the very kind your own Copilot platform popularized) asking about your 45-million-tonne program has nothing structured to read; a simple agent surface means that story gets read right, from you.
Microsoft is regularly conflated with Frontier (which it never joined) while buying directly at a scale nobody else hits; publishing that as machine-readable fact means an AI answers the question accurately instead of guessing from scraped prose.
Microsoft's own newsroom states it plainly: 45 million metric tonnes of carbon dioxide removal were contracted in fiscal year 2025, doubling FY2024's volume and running nine times FY2023's. The deals span 21 supplier companies across enhanced rock weathering (Lithos Carbon), regenerative farming (Agoro Carbon Alliance), BECCS (Stockholm Exergi), and tropical reforestation (re.green), with projects in the US, Brazil, Denmark, Sweden, Bolivia, Norway, India, Panama, Canada, and Switzerland. External corroboration (CTVC, cited in our earlier public research on Frontier) separately estimates Microsoft controls roughly three-quarters of the entire voluntary CDR market by volume.
Source: news.microsoft.com/source/features/sustainability/from-farms-to-oceans-how-microsoft-is-working-to-scale-carbon-dioxide-removal
Our earlier public research on Frontier Climate independently confirmed, directly against frontierclimate.com/who-we-are's own member-logo markup, that Microsoft has never appeared as a Frontier member, buyer, or supplier. Microsoft buys removal directly on its own contracts (finding 1) and separately co-founded the Symbiosis Coalition in 2024 with Google, Meta, and Salesforce, an advance market commitment for nature-based removal (afforestation, reforestation, mangroves) targeting 20 million tons by 2030, explicitly modeled on Frontier's own AMC playbook but run as a structurally separate organization for a different removal category.
Sources: symbiosiscoalition.org/perspectives/launch-press-release · from earlier public research (internal working notes)
llms.txt (the file AI assistants read first), .well-known/agent-card.json, and .well-known/ai-plugin.json all return a true HTTP 404 with an identical 784,306-byte body, matching a nonsense-path control exactly. robots.txt exists and returns 200, but is a plain, standard crawler directive file, nothing agent-specific. For a company whose own AI agent platforms (Copilot, Azure AI Foundry Agent Service) are among the most widely deployed in the enterprise world, its own marketing domain has no equivalent front door for an external agent to read.
Sources: microsoft.com/llms.txt · microsoft.com/.well-known/agent-card.json · microsoft.com/robots.txt (checked 2026-07-16)
This isn't a Microsoft-side finding; it's the note this brief exists to make. Microsoft's 45 million tonnes are real, contracted, and delivered over years at facilities almost no employee will ever see. EWP's work-packet lifecycle (fund → claim → prove via photo+GPS+signature → approve → on-chain settlement, live on Base mainnet) runs the identical shape at a scale a single person can watch happen: a receipt-backed, tCO2e-mapped, local action instead of a tonne bought sight-unseen. Microsoft's own agent platforms are exactly the kind of tool-calling runtime that could consume an x402-priced EWP packet directly; no integration exists or is claimed; this is an honest observation of fit, not a pitch.
Internal working notes (fund/claim/prove/settle lifecycle) · basescan.org/address/0x76c17C51336BE7B39F5164802e08b9811477A14B (source-verified contract)
Nothing here is a security finding or a broken product; Microsoft's removal scale is genuinely the largest we've reviewed, credited in full. The pattern is narrower: one common conflation worth correcting (finding 2) and one clean, total agent-discovery gap (finding 3) sitting alongside a program whose entire value proposition is "we buy more removal than anyone." EWP's packet-scale lifecycle already runs the same contract shape Microsoft's suppliers operate under, just small enough for a single person to see settle.
