Platform

Four layers. One chain of evidence.

Instrumentation in the field, verification that can't be shopped for, a registry anyone can audit, and an API that puts all of it into your own systems.

0
API uptime
0
Platform layers
0
Official SDKs
Platform stack Live
MRV Suite
Sensors, satellite, lab pipelines
Verification layer
Rotation-assigned, registry-funded
Public registry
Issuance & retirement records
Developer API
REST + webhooks, 99.95% SLA
The stack

Each layer produces evidence the next one depends on

Nothing here is optional or bolt-on. Remove any layer and the chain of evidence breaks.

Instrumentation workspace
What a credit record contains

Everything an auditor would ask for, already attached.

Open any credit on the registry and you get the full provenance without filing a request or signing an NDA.

  • 01 Raw instrument readings with timestamps and calibration history
  • 02 Methodology version applied, with a diff against the previous version
  • 03 Verifier identity, assignment date, and signed attestation
  • 04 Site coordinates, batch ID, and complete retirement chain
Developer API

Everything the dashboard does, over REST.

The web app is a client of the same API you get. Query inventory, execute purchases, retire credits, and stream verification events into your own systems.

Uptime SLA
99.95%
Auth
OAuth 2.0
SDKs
JS · Python · Go
Sandbox
Free, unlimited
Request API access
# 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://…"
}
Technical questions

What engineering teams ask

Yes — issuance records, retirement records, measurement data, and verifier attestations are all readable without authentication. You need an API key for write operations and portfolio-specific endpoints, but auditing the public record requires nothing from us.

Read endpoints allow 1,000 requests per minute per key. Write endpoints allow 60 per minute. Bulk retirement operations are queued and return a job ID rather than blocking. Limits are raised on request for legitimate integration volume.

URL-based versioning with a minimum 12-month deprecation window and email notice at 12, 6, and 1 month. Breaking changes only ship in a new major version — v1 endpoints will behave the same in five years as they do today.

Most likely. We maintain integrations with the common carbon accounting platforms and the API is straightforward for custom stacks. Webhooks push retirement and verification events as they happen, so you're not polling.

Yes, free and unlimited, with a full set of synthetic projects and credits. Sandbox keys are issued instantly and never touch production data or real credits.

See it working

A walkthrough with real data, not slides

We'll open the actual registry, pull a live credit record, and show you the measurement data behind it.