Instruments in the field, a verifier nobody gets to shop for, a registry open to anyone, and an API that drops the lot into your own systems.
None of it is optional. Pull out any one layer and the trail stops there.
Field sensors, satellite pipelines, lab assay feeds and automated batch reports. We fit the hardware, recalibrate it on a schedule and hold the raw data. Nobody self-reports here, because there is nothing left to self-report.
Explore
Accredited verifiers drawn by rotation and paid from a pooled fee. Every attestation is signed and goes public.
ExploreEvery issuance and retirement is a permanent record you can query, with its full trail attached.
ExplorePermanence-weighted exposure, blended cost per tonne, and where you stand against a science-based target.
Open any credit in the registry and the whole history is there. No request form, no NDA.
Our web app is just a client of the API you get. Query inventory, buy, retire, and stream verification events straight into your own systems.
# Retire credits against a target POST /v1/retirements { "portfolio_id": "pf_02H8K4M1", "amount_tco2": 1250, "beneficiary": "Acme Corp", "vintage_year": 2026 } # 200 OK { "retirement_id": "ret_02H8L9Q3", "status": "complete", "credits": 1250, "pathways": [ "biochar", "weathering" ], "attestation_url": "https://…" }
Issuances, retirements, readings and verifier attestations all read without authentication. A key is needed for writes and for your own portfolio endpoints, but going through the public record needs nothing from us at all.
Reads run at 1,000 requests a minute per key, writes at 60. Bulk retirements queue and hand back a job ID instead of blocking. Ask and we'll raise the ceiling for real integration volume.
Versions live in the URL, with a 12-month minimum deprecation window and email at 12, 6 and 1 month out. Breaking changes only ever land in a new major version, so a v1 endpoint will behave the same in five years as it does now.
Very likely. We keep integrations with the common carbon accounting platforms, and the API is plain enough for an in-house stack. Webhooks push retirement and verification events as they land, so nothing has to poll.
Free, unlimited, and stocked with synthetic sites and credits. Keys issue instantly and never touch production data or a real credit.
See it working
We'll open the registry, pull a credit at random, and show you the readings sitting under it.