nset.io / for-traders
For traders & processors
The Scope 3 pull is already landing on you. Bring the measurement you already have — no rebuild, no new MRV — and we get it to issuance-grade against one conformance standard, ready to move into a real transaction with a customer you already serve.
One verified score, allocated across byproducts
Verified CI score
Corn · IA supply shed
0.31 tCO₂e/t
↓
Corn oil · 3% of mass
0.01 tCO₂e/t
DDGS (feed) · 30% of mass
0.09 tCO₂e/t
Starch · 67% of mass
0.21 tCO₂e/t
↓
All three become priced, transferable certificates
01
How your CI scores become downstream value
Your program generates carbon-intensity scores across many origins. The allocation engine pools the verified total and allocates it back out across every downstream SKU or byproduct stream sourced from that pool — never issuing more than was verified in.
Verified origins
Field / lot A
38 t
Field / lot B
29 t
Field / lot C
33 t
Each carries its own Tier 3 CI score, measured at the source.
Mass-balance pool
100t verified in
Verified performance from every origin is credited into one ledger — commingled the same way the physical commodity is.
ALLOCATED OUT
≤ 100 t
Downstream allocations
Byproduct stream 1
42 t
CIC issued
Byproduct stream 2
31 t
CIC issued
Byproduct stream 3
27 t
CIC issued
42 + 31 + 27 = 100 t — allocated out never exceeds verified in.
Why it matters to you — Each allocation is its own certificate, priced and transferable on its own — so one program with mixed supply can serve several buyers at once without over-crediting any of them.
02
Built for inventory claims
Every certificate this program produces is checked against the same three tests — measurable, additional, permanent — before it can be priced, packaged, and transferred.
SBTi FLAG
· land-sector target guidance
GHG Protocol
· Scope 3, Category 1 accounting
ISO 14067
· product carbon footprint
ISO 22095
· chain of custody
03
Bring your own MRV — or use ours natively
The rail doesn’t care where your data comes from — it cares that it clears the standard. The same conformance adaptor normalizes whatever you already run into issuance-grade evidence, and flags gaps instead of rejecting the program outright.
Bring your own MRV
Keep your existing provider
Your program’s existing measurement — field records, third-party MRV, satellite or soil data — enters through the same conformance adaptor as anything else. No re-platforming, no new supplier relationships.
Native primary MRV
Or measure natively, with Hyphen
Programs without full field-level coverage can measure directly on the rail through our native integration with Hyphen — Tier 3 primary data flows straight into issuance, with no separate MRV contract to manage.
Not sure where your program’s data stands against the conformance bar? Get your readiness review.
04
Deploy the rails
Four steps from your existing supply to a transferable certificate — no new measurement stack, no new supplier relationships.
01
Onboarding · days
Keep your measurement.
Bring your own MRV provider or use the Hyphen primary-data stream — the rail is MRV-agnostic.
02
Before harvest
Connect your supply shed.
The allocation engine ties your program’s verified performance to real commodity volume.
03
After harvest
Issue certificates.
Once the physical commodity is measured and processed, performance is cleared and issued into the registry as transferable instruments.
04
Every cycle
Ready for transfer.
Priced and evidenced, the certificate is ready to move directly into a buyer’s inventory — run today as a direct transaction, with your relationship intact.
Because a certificate is tied to a physical commodity, issuance follows harvest and processing — not a software onboarding clock.
Coming soon
Direct, hands-on deals are how transactions move today — that’s what builds trust into the settlement layer underneath. The marketplace extends your reach beyond the buyers you already know: we bring book-and-claim demand to your listings and help you commercialize performance that would otherwise sit unclaimed.
Your listings, matched to book-and-claim buyers…
Corn oil · 42t
0.01 t
matching…
DDGS (feed) · 31t
0.09 t
matching…
Starch · 27t
0.21 t
matching…
Illustrative · book-and-claim matching on the roadmap
05
The problem
Each vendor solves one slice — measurement, or a registry, or a marketplace, or reporting. None of them is the rail that connects your program’s performance to a downstream transaction. You end up stitching them together yourself.
Function
MRV vendor
Standalone registry
Marketplace
Reporting tool
Nset rails
Measurement intake
✓
–
–
–
✓
Allocation & custody
–
~
–
–
✓
Audit & clearing
–
✓
–
~
✓
Package & price data
–
–
~
–
✓
Move into transactions
–
–
~
–
✓
✓ covers · ~ partial · – doesn’t. Vendor types shown as categories, not named products.
No point solution owns a full column — each covers one function, at best, with gaps everywhere else. Nset owns the whole row — the connective infrastructure that turns measurement, custody, clearing, and pricing into one instrument your program can actually transact on.
Frequently asked
How do I generate value from my regen-ag program?
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.
Do I have to replace my current MRV or program tools?
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.
What if my program spans multiple commodities?
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.
Who sets the price on a marketplace listing?
You do. Nset provides the pricing mechanics and reference data so a listing is comparable and defensible, but the trader or program operator sets the price — Nset does not fix it.
Bring the program and the supply. We bring the rail that turns its performance into transferable value.