ZerraLedger sits between government SAF certificate registries and the platforms that need to consume that data — ingesting, normalising, and reconciling across schemes so developers don't have to.
ZerraLedger connects directly to government-operated SAF certificate registries and publication systems — not scrapers or manual uploads. Data is ingested at source, preserving provenance from the point of issuance.
The Australian Clean Energy Regulator (CER) Guarantee of Origin API is the first live connection. CORSIA eligible fuels data is ingested from ICAO publication cycles. EU, UK, and Singapore registries follow as they become API-accessible.
CER API connected CORSIA ingestion in development EU · UK · Singapore roadmapEach SAF scheme — Australian GO, CORSIA, EU RefuelEU, UK SAF mandate, Singapore CAAS — uses different data structures, fuel pathway taxonomies, and certificate identifiers. ZerraLedger normalises all of them into a single, consistent schema.
Certificates are stored with vector embeddings enabling semantic search across fuel pathways and scheme descriptions. A longitudinal archive is maintained across all scheme updates — queryable back to ingestion.
The reconciliation engine maps normalised SAF certificates against compliance obligations — by route, reporting period, fuel pathway, and scheme eligibility rules. It flags coverage gaps, potential double-counting, and cross-scheme eligibility conflicts automatically.
The core use case today: mapping Australian Guarantee of Origin certificates against CORSIA Phase 1 obligations for international routes. As more schemes come online, the engine handles multi-scheme portfolios — an airline operating across EU, UK, and CORSIA simultaneously.
Every reconciliation result is returned as a clean JSON response — structured for direct ingestion into carbon accounting platforms, travel management systems, or ERP sustainability modules. OpenAPI 3.1 specification available for developer evaluation.
No derived or estimated values. Every figure in the API response is traceable back to a government-issued certificate. Timestamp, registry source, and ingestion record included in every response.
View endpoint reference →Every certificate reference returned by the ZerraLedger API is timestamped against source registry data at ingestion. No derived or estimated values enter the pipeline. The full audit trail — from API response back to the government-issued certificate — is available on every request. This is the trust layer that compliance reporting requires.
The SAF regulatory landscape is fragmented by design — each jurisdiction has its own certificate format, eligibility criteria, and reporting period. ZerraLedger is the interoperability layer across all of them.
Ready to evaluate the API for your platform?