Built from public reporting on the Mardie char project plus a fresh live probe of biomassprojects.com.au. Every claim below cites its source and a re-runnable command.
Biomass Projects is developing what public reporting describes as the world's largest biochar production facility on a 225,000-hectare Pilbara, Western Australia plot overrun with invasive mesquite. The stated target is 500,000 tonnes of CO2 removal annually by 2028; the full build is projected to pyrolyse 10.5 million tonnes of biomass over 20 years, removing 10.2 million tonnes of CO2. Carbonfuture provides dMRV; Residual provides credit ratings, insurance, and offtake strategy.
The project partners directly with the Wirrawandi Aboriginal Corporation, which represents the Mardudhunera and Yaburara peoples on whose land the project operates. The ecological rationale is concrete: invasive mesquite across a 300,000+ hectare regional infestation drains an estimated 11 billion cubic meters of groundwater per year (described elsewhere as roughly the equivalent of Lake Tahoe every decade), and removing it is expected to allow native species and natural habitats to regenerate.
Unlike Exomad Green's already-operating megatonne scale, Biomass Projects is a pre-revenue, first-of-a-kind industrial build still in permitting/construction, precisely the "missing middle" Carbonfuture's own financing thesis describes: too big for grants, not yet proven enough for a $50M+ offtake-securitized project-finance package. That gap operates at the plant level (single-digit-million-dollar CAPEX, multi-year construction), a different unit of scale entirely from EWP's sub-dollar packets, worth naming honestly rather than overstating EWP's relevance here.
biomassprojects.com.au ships a real, working robots.txt (the file that tells search engines what to index; 200, 123 bytes, standard WordPress Disallow: /wp-admin/, pointing at a real wp-sitemap.xml). But llms.txt (the file AI assistants read first), ai.txt, .well-known/agent-card.json (the file that lets an AI assistant use a site correctly), and openapi.json all return a TRUE HTTP 404: a 54,647-byte error page, byte-identical to a nonsense-path control fetched in the same pass. Zero agent-legible surface today, which is unsurprising for a project still in the permitting/construction phase rather than a market-facing platform.
