Every question, in one place.

A verified digital record of primary-data environmental performance tied to a physical commodity. It moves with the goods via mass balance and lands in a buyer's Scope 3, Category 1 inventory as an audited reduction.

A CIC represents inventory-linked performance measured at the source and stays attached to the commodity. An offset compensates for emissions elsewhere and is detached from the goods. CICs count toward supply-chain reductions; offsets increasingly do not survive audit.

No. Every certificate has one ID and one lifecycle in the registry. Once retired against a claim it is spent and cannot re-enter another inventory.

Yes. A CIC starts with primary performance at origin, but the same canonical schema can layer packaging, energy, and transportation data onto the certificate, so it reflects a fuller cradle-to-gate intensity rather than origin alone.

The four-layer infrastructure that turns verified performance into a tradable instrument: data ingestion, allocation, audit & clearinghouse, and the registry. Every certificate passes through all four, in order, before it can settle in a buyer's inventory.

No. Traders and processors plug into ingestion and allocation to generate certificates; buyers interact mainly with the registry and the evidence pack it produces. The rail runs underneath either way.

Yes. Corn, soy, wheat, canola, cotton, beef, pork, poultry, and dairy all run through the same four layers — only the measurement inputs and allocation math change per commodity.

No. Nset is MRV-agnostic. Performance can enter as primary Tier 3 data through our measurement partner Hyphen, or through BYOM, where any provider submits observations into a canonical schema. The legal instrument never depends on a single black-box model.

A provider-agnostic MRV adapter. Each provider submits observations into Nset's canonical MRV object, so the rail can ingest many providers' outputs without rewriting the instrument and without vendor lock-in.

Every MRV claim carries version metadata. When an estimate changes, the rail distinguishes whether the real world changed, the dataset changed, or the model changed — so a certificate reprices on genuine performance, not on model drift.

It connects verified performance to a specific commodity flow and carries it downstream — using mass balance, supply-shed attribution, and chain of custody — so a number measured at origin still attaches to the exact goods a buyer purchases after blending and processing.

Through mass balance. The credited volume entering a pool is tracked, and the credited volume leaving can never exceed it, so a proportional, evidenced share of the reduction attaches to the byproduct without over-issuance.

When goods can't be traced to a single origin, the engine attributes measured performance across the defined supply shed the buyer actually sources from, weighted by each origin's contributed volume — so the reduction is tied to real volume, not a regional average.

Yes. The ledger tracks credited volume in and credited volume allocated out across every certificate drawn from a pool, regardless of how many buyers or downstream commodities draw from it — the sum of allocations can never exceed the verified total.

It clears each certificate exactly once. Single-use retirement means a reduction is claimed a single time and cannot re-enter another inventory — the mechanism that makes double-counting structurally impossible.

An independent third-party verifier reviews the measurement evidence, the allocation math, and the custody trail before a certificate clears — with no stake in the volume issued.

By a fixed five-step workflow — flag, freeze, review, rule, resolve — so conflicts settle by rule rather than case-by-case argument.

Every MRV claim carries version metadata. The clearinghouse distinguishes real-world change, dataset revision, and model revision — only real-world change ever reprices a live certificate, and retired certificates are never restated.

Issue, transfer, transform, settle, and retire certificates in one source of truth. Verified supply also surfaces to buyers through the marketplace, an early-access procurement layer built on top of the registry.

When a buyer confirms a purchase, the registry matches the certificate, transfers custody, and settles the transaction atomically — custody and payment move together, so neither side is exposed mid-transfer.

Issuance, transfer, and retirement are visible in the public registry as a single source of truth. Buyer identity, negotiated price, and pre-onboarding volumes stay private; the certificate ID, commodity, vintage, and status do not.

No. A CIC is not sold as a standalone financial asset — it is unbundled and re-attached to a physical commodity only as part of a real transaction, never traded independently the way a security is.

Deploy the Nset rails into the program you already run. Verified carbon-intensity performance is packaged and priced as a transferable Carbon Inventory Certificate, which moves into downstream commodity transactions rather than being negotiated deal by deal.

No. Nset is neutral, MRV-agnostic infrastructure. Bring your own measurement provider or use ours; the rails unify fragmented point solutions into one instrument rather than replacing what already works.

Each commodity or supply shed runs through the same rail independently. The allocation engine pools and issues certificates per commodity, so a multi-commodity program doesn't need separate systems or separate onboarding for each one.

Attach verified, inventory-linked performance to a commodity you already buy. Nset issues primary-data reductions as Carbon Inventory Certificates and retires them into Scope 3, Category 1 in the current cycle — instead of waiting on modeled estimates or supplier surveys.

Accounting platforms measure and report your footprint. Nset delivers the reduction itself — an audited, transferable instrument that lands as supply-chain inventory, not just a number in a dashboard.

CICs are built on Tier 3 primary data with chain-of-custody evidence aligned to ISO 22095, and single-use retirement, so each reduction is traceable to a specific purchase and cannot be double counted — the properties an audit of supply-chain reductions requires.