Answered the way we'd answer on a call. Where the true answer is "we haven't built that yet," that's what it says.
Showing all 21
We sit underneath durable carbon removal and do the measuring. Instruments go onto the site, an independent verifier is assigned and paid by us, credits are issued to a public registry, and every tonne keeps a record a buyer can follow. We are not a broker and we never hold a position in the credits.
Removal only. Avoidance and reduction credits are not listed here at all. Every tonne is carbon physically taken out of the air and held for a stated period.
Biochar, enhanced rock weathering, direct air capture into geological storage, and native-species reforestation. Blue carbon and bio-oil we take case by case.
Melbourne, with sites in twenty-four countries.
Entirely down to pathway. Reforestation runs $45–95, biochar $120–180, enhanced weathering $180–320, direct air capture $380–600. Most buyers end up with a mix somewhere between $90 and $160, and multi-year offtake pulls all of those down.
Spot starts at 100 tonnes. Offtake usually starts at 1,000 tonnes a year, which is where the price and supply-security advantages show up. Under 100 tonnes we'll generally point you somewhere better suited.
All of it, before you commit to anything. Readings, method version, verifier attestation and site details are public for every site. You can work through one completely without speaking to us.
Retirement records export in formats lined up with GHG Protocol and SBTi guidance, and the API pushes into most carbon accounting platforms. If you've built something in-house, the REST endpoints are documented and we don't move them.
A buffer pool, funded by a slice of every issuance across all four pathways, sits behind this. If a confirmed reversal touches credits you've already retired, replacements come out of the pool and cost you nothing. We publish the balance monthly.
Yes, and we'd rather you did. Site access is written into every offtake agreement. We set the visit up with the developer, and with the verifier too if you want the technical version.
Nothing up front. Instruments, verification and platform costs come back as a share of issuance, so we're paid when you are. The share moves with pathway and volume, and you get the number before committing to anything.
Four weeks is the median: three days on eligibility, about a week on the method review, two weeks to install and calibrate, then your first measured batch.
The operational data stays yours. Readings attached to issued credits get published, which is the entire point of the model and is written plainly into the agreement. Your commercial terms, costs and internal operations never appear.
Yes, unless you've signed a specific exclusive. Most developers run a mix. The one rule is that a tonne measured on our instruments can't also be issued somewhere else.
Common, and not a problem. What matters is whether the removal mechanism is sound and measurable. We've taken sites on at pilot scale and paid up front to fund the build.
Three questions: is the removal physically real and measurable, does it hold for a defined period, and are the land-rights and community safeguards real rather than drafted. We decline more than we accept, and we always say why.
We do, out of a pooled fee taken at issuance. A developer never picks their verifier and never pays one, and verifiers rotate between sites. The separation lives in the plumbing rather than in a policy document.
A normal registry files what the developer sends. We produce the measurement ourselves on hardware we install and maintain, hand the audit to a verifier chosen by rotation, and publish the raw readings with the credit. Recording it is the last step here, not the whole job.
The methods are written against the ICVCM Core Carbon Principles, and the claims guidance we give buyers follows the VCMI Claims Code. Retirement records are structured for GHG Protocol reporting and the incoming EU CRCF.
A tonne measured on our instruments cannot be issued through another registry, and that's contractual with every developer. Retirement is permanent and public, so reselling a retired credit is visible to anyone who looks.
When the science calls for it, usually once or twice a year per pathway. Every version is kept, and a credit stays tied to the version that was in force when it was issued.
Still stuck?
Technical questions go to the science team instead of through sales. Flag it in your message and we'll send it that way.