Underwriting-grade collateral verification API that lets trade-credit insurers price agri export finance in real time.

1. An insurer, not just financial investors, led the funding round for a tokenized agri-verification platform, showing underwriters are now willing to pay for this category directly.
2. Three years of live operations and 4,000-plus smart contracts with a 70 percent repeat rate show verified agri-asset infrastructure has moved past pilot stage into repeatable commercial demand.
3. Framing the platform as pursuing the world's first regulated agricultural exchange suggests regulators are actively being engaged, lowering compliance risk for adjacent risk-data providers entering the same corridors.
4. Published patents around agri tokenization signal a defensibility race is starting, making now the right time to stake out the underwriter-facing risk-data layer before it gets bundled into a single exchange's IP.

Catalyst. An insurer publicly leading a tokenized agri-verification funding round signals that underwriters are now actively budgeting for this category rather than waiting for exchanges to mature around them.

Deploy a lightweight verification stack at origin (IoT container/custody sensors, satellite and customs data feeds, and a network of vetted independent surveyors) that continuously attests to a shipment's quality, custody chain, and location from warehouse to vessel. This data feeds a risk-scoring API that insurers call directly from their underwriting systems to price a policy or approve a credit line before goods leave port, and again at key custody transfer points to catch diversion or substitution before a claim event. The scoring model and verification records are portable, so an insurer or lender is not locked into any single exchange or marketplace to benefit from the data.

What's different. Unlike an exchange or marketplace operator, this product does not ask insurers or exporters to move their trading activity onto a new platform. It sells the underwriting desk a portable risk score they can drop into policies and credit lines they already write, regardless of which exchange, bank, or broker the shipment ultimately clears through. That neutrality lets it become the risk-data layer of record across multiple competing agri-exchanges rather than betting on any single one winning the marketplace war.

Jobs to be done

flowchart LR
  Shipment[Cocoa/cashew export shipment] --> Oracle[IoT custody + customs + surveyor oracle]
  Oracle --> RiskAPI[Agri Collateral Risk API]
  Insurer[Trade-credit insurer underwriting desk] --> RiskAPI
  RiskAPI --> Score[Verified collateral risk score]
  Score --> Policy[Priced trade-credit policy or credit line]
  Policy --> Exporter[Exporter receives financing]

Executive takeaways

• There is real budget pain to solve: West African trade finance still prices letters of credit at roughly 2–4% of transaction value, banks often ask for extra collateral, and trade credit insurance remains lightly penetrated globally and especially unfamiliar in West Africa [14][9].
• The wedge should be a neutral underwriting layer, not another marketplace: adjacent players each cover only one slice—exchange liquidity, document/title control, workflow, or telemetry—but not all three together [1][39][43][45][47].
• Regulatory timing is favorable because MLETR, the UK ETDA, eBL interoperability frameworks, and EUDR all reward auditable digital custody and compliance trails [21][22][24][25][29][30][31].
• The near-term market is real but initially narrow; proving one corridor and 4-5 insurer logos can support a low-single-digit-million SOM, while venture scale requires expansion into more commodities, corridors, and lender/exchange data products [33][34][35].

Market definition

The relevant market is underwriting and risk infrastructure for agricultural export finance: software and data services that help trade-credit insurers, ECAs, and commodity lenders verify title, custody, condition, and compliance for export collateral before and during shipment [14][16][21][23][29].

Customer and buyer

Daily users are underwriting, risk operations, and claims teams at regional trade-credit insurers and export credit agencies, with commodity lenders and trade-finance banks as secondary stakeholders. The economic buyer is usually the head of underwriting or CRO, especially where West African trade finance remains expensive and collateral enforcement is weak [14][9][19][20].

Buying triggers

• Loss-ratio or claims review after a fraud, misdelivery, or document dispute exposes how little confidence the desk has in paper and email chains. [17][18][37][48]
• Portfolio growth into West African cocoa or cashew corridors is constrained by high LC costs and weak collateral enforcement, making better pre-bind verification attractive. [14][16][19][20]
• EU-bound cocoa programs now need richer traceability and due-diligence data, pulling insurers closer to compliance-grade evidence rather than broker attestations. [28][29][30][31]

Willingness to pay

Buyers already absorb high LC spreads, extra collateral demands, and manual control costs. If the API can improve advance rates, speed approvals, or shrink claim investigations, it can slot into existing risk-management spend rather than inventing a new budget line. [14][16][17][18][39][47]

Category dynamics

Growth signal 33.0% to 49.2% eBL user adoption from 2022 to 2024 (~22% annualized)

Validation signals

• An insurer, Tawuniya, led Maalexi’s 2026 round after the company logged 36 months live, 4,000+ smart contracts, and a 70% repeat customer rate—direct proof that underwriting-adjacent buyers will back this category.
• The IFC/WTO West Africa study shows banks already pay with time and margin for poor visibility: LC pricing is 2–4% and extra collateral is common.
• Ghana’s warehouse-receipt rollout showed zero defaults in the cited pilot and 32 rural/community banks connected to the e-WRS system, suggesting structured collateral evidence can change lender behavior on the ground.
• eBL adoption reached 49.2% in the 2024 ICC/FIT survey and interoperable, IGP&I-approved cross-platform exchange is now live, reducing one major document-side objection.

Regulatory & technical constraints

• Electronic bills of lading and warehouse receipts only work as underwriting evidence if the chosen system can prove control, integrity, uniqueness, and approved rulebooks under MLETR-style or ETDA-style regimes.
• EU-bound cocoa shipments increasingly need geolocation-linked due-diligence statements and operator workflows under EUDR.
• Banks in ECOWAS4 still report asking for extra collateral because merchandise can be hard to seize and resell, so digital evidence must improve enforceability, not just visibility.
• Interoperable eBL still depends on shared legal annexes, control registries, and club-approved platforms; not all jurisdictions or participants are ready.

Competition is fragmented across exchange operators, document/title networks, trade-finance workflow software, collateral managers, and cargo-visibility vendors. No cited incumbent combines physical collateral control, document-title control, and underwriting-native scoring in one exchange-agnostic API [1][39][43][45][18][47].

Why incumbents do not win by default

• Exchange operators. Maalexi proves insurer-backed demand, but its center of gravity is a regulated agricultural exchange and tokenized venue; a neutral API can win buyers that do not want to bet on a single marketplace.
• Trade-finance workflow suites. Komgo is strong at structured instrument workflows and document audit trails, but it is still workflow-centric and broad across industries rather than a corridor-specific physical-collateral score for underwriters.
• eBL and digital-original networks. CargoX, WaveBL, and Enigio solve title-document authenticity and transfer, yet they stop short of continuous cargo-condition, custody, and counterparty risk scoring.
• Collateral managers and surveyors. Manual CMA/SMA operators create real control and recovery value, but they are episodic, service-heavy, and hard to plug directly into underwriting decisions in real time.
• Cargo-visibility platforms. ORBCOMM and Overhaul provide telemetry and security signals, but they are not underwriting systems of record and do not on their own establish document title or release control.

Agri Export Collateral Risk Oracle is a pre-seed underwriting API that helps trade-credit insurers and export credit agencies price West African agricultural export risk using verified custody, quality, and traceability data instead of paper certificates and episodic surveys. The beachhead is mid-size Gulf and West African insurers underwriting West African cocoa and cashew export books, starting with EU-bound cocoa from Ghana and Côte d’Ivoire because EUDR and recurring fraud pressure create the sharpest buying trigger there. The first product is not an exchange, lender, or workflow suite; it is a corridor-specific pre-bind risk score and handoff-alert layer that plugs into existing policy issuance and credit-approval flows. Research supports the timing: West African trade finance still carries high friction and extra collateral demands, eBL adoption has risen, and an insurer led Maalexi’s funding round, showing that underwriting-adjacent buyers will fund verified agri-trade infrastructure. Go-to-market should pair founder-led sales to heads of underwriting and CROs with corridor partners such as surveyors, collateral managers, and document platforms so the first pilot can be sold during renewal or post-loss review without asking customers to replatform. The modeled beachhead market is real but still modest at an estimated $14.1M SAM and $2.0M year-3 SOM, so this only becomes a venture outcome if the company earns the right to expand corridor-by-corridor into adjacent commodities, lenders, and reinsurer data products. The biggest execution risk is not software quality alone but whether local data partners can deliver trustworthy pre-bind evidence with enough coverage and low enough corruption risk to change underwriting decisions. Research also leaves two critical gaps unresolved: which specific 4-5 insurers control enough relevant volume to anchor the first pilots, and what share of target corridor shipments is actually insured rather than handled on open-account terms.

Problem

• Underwriters still price cocoa and cashew export books from paper certificates, bills of lading, broker attestations, and periodic surveys, so diversion, substitution, or misgrading is often discovered only after a claim.
• Weak collateral enforceability and rising traceability requirements push insurers and lenders to overprice risk, demand extra collateral, or cap exposure in corridors where exporters still need financing.

Solution

• Aggregate surveyor attestations, eBL or customs document events, and custody telemetry into a corridor-specific pre-bind risk score and audit trail that fits existing underwriting workflows.
• Monitor the same shipment at warehouse and port handoffs, push exception alerts into underwriting or claims operations, and keep the evidence portable across banks, brokers, and exchanges.

Why we win

• The product gives insurers a neutral API they can buy without betting on one exchange, unlike Maalexi-style venue strategies.
• The wedge sits exactly where budget and urgency already appear: renewal reviews, loss-ratio reviews, and EU cocoa programs that now need more auditable evidence.
• Claims-linked corridor data, partner performance history, and document-to-telemetry graphs can compound into a more defensible underwriting model than point document or IoT vendors provide.

Milestones

flowchart LR
  Wedge[EU cocoa insurer wedge] --> MVP[Pre-bind score plus custody alerts]
  MVP --> Proof[Pilot loss and quote-speed proof]
  Proof --> Expansion[More corridors commodities and data buyers]

Founding team

Experiment roadmap

Risk assessment

What must be true

• Four to five insurers or ECAs in the beachhead control enough West African cocoa or cashew volume to support a concentrated first-logo strategy.
• Pre-bind evidence from surveyors, customs, documents, and telemetry is available on most pilot shipments early enough to change underwriting decisions.
• One corridor pilot can improve quote turnaround or manual-review load by at least 30% and surface exceptions manual processes miss.
• Local partner SLAs can hit data-completeness and anti-corruption thresholds without collapsing gross margin into a services business.
• Insurers value exchange-neutral portability enough to buy a standalone API instead of waiting for exchange or document vendors to bundle similar features.

Open diligence questions

• Which named Gulf and West African insurers or ECAs have the highest cocoa or cashew insured volume and recent fraud or claims pain?
• How much decision-useful data is actually available before bind versus only after a shipment is already moving?
• Which KPI matters most to the buyer in practice: loss ratio, quote turnaround, advance rate, or claim-investigation time?
• Can surveyor, warehouse, and document partners meet anti-corruption and uptime SLAs across Ghana and Côte d’Ivoire at acceptable unit economics?
• Will reinsurers and brokers introduce this as a loss-control tool, or view it as added operational friction?

Model sanity

• Revenue engine. Base-case revenue comes from growing active paid corridor accounts from 2 at Y1 exit to 6 at Y3 exit while blended account ARPU rises from pilot-heavy ~$28K months to ~$37K months.
• Must go right. The company must land a first paid pilot by M6 and keep partner and data costs below the BP's 30% ceiling so gross margin can clear 70% by Y3.
• Model breaks if. If the sales cycle stretches toward 8-9 months or partner data quality delays production pricing, downside revenue falls to about $1.5M and cash dips roughly $0.4M below zero.
• Next-round proof. A seed story exists once the pre-seed gets the company to 3 paid or production accounts by Month 18 and 4 active corridor accounts by Month 24 with a referenceable underwriting ROI case.

Scenarios

Sensitivity

flowchart LR
  TargetAccounts --> PaidPilots
  PaidPilots --> CorridorAccounts
  CorridorAccounts --> MonitoredShipments
  MonitoredShipments --> Revenue
  CorridorAccounts --> BenchmarkData
  BenchmarkData --> Revenue
  Revenue --> GrossProfit
  GrossProfit --> Cash

Flags: Y3 still runs at a negative EBITDA margin, so the next round depends on corridor repeatability and underwriting ROI proof rather than profitability. · Four to six active corridor accounts likely represent only 4-5 insurer logos, so one delayed anchor logo can move annual revenue by roughly $0.3-0.4M. · Gross margin only clears 70% if partner and data-feed costs stay below the BP's 30% ceiling by the third pilot. · The model assumes 70%+ pre-bind data completeness and a first paid pilot in M6; if either slips, the downside case goes cash negative.

• Exchange platforms vertically integrate underwriting. Maalexi or similar exchanges could build their own insurer-facing risk-scoring layer, cutting out a standalone verification provider. Mitigation: Sell directly to insurers as an exchange-agnostic layer with contractual data portability, keeping the insurer relationship primary rather than routing through any single exchange partnership.
• Physical verification can still be gamed. Bribed surveyors, spoofed sensors, or falsified custody records could undermine the risk score insurers rely on, causing a trust-destroying failure. Mitigation: Require multi-source corroboration (IoT telemetry, customs/satellite data, and independent surveyor sign-off) with cryptographic anomaly detection before a score is issued.
• Regulatory and corridor fragmentation slows expansion. Insurance and trade-finance rules differ sharply between West Africa, the Gulf, and the EU, lengthening sales cycles and complicating a single compliance playbook. Mitigation: Launch with one insurer in one corridor, build a documented compliance and integration playbook, then replicate corridor-by-corridor with local reinsurance or ECA partners.