Skip to main content
MicroCrop is parametric insurance infrastructure for African smallholder farmers. As a partner — an insurer, reinsurer, cooperative, MFI or agtech platform — you integrate our API to register farmers, price and sell index cover, and get a signed, independently verifiable determination of whether the trigger fired and by how much. What we do with the money after that is a commercial choice, and it is the one decision that shapes your whole integration:

DETERMINATION (Tier 1)

We determine. You settle the farmer, off-platform, off your own balance sheet. We never touch the money.

DETERMINATION_AND_SETTLEMENT (Tier 2)

We determine and originate and settle the payout to the farmer.
New organizations start on DETERMINATION. Read Service tiers before you build anything.

​
What you can build

Onboard farmers

Register farmers and their plots or herds, with KYC.

Quote & sell cover

Price crop (sum-insured) and livestock (IBLI) cover, then issue policies.

Verifiable determinations

A signed, chain-neutral, currency-neutral determination plus an evidence package your regulator or reinsurer can re-verify without asking us anything.

Settlement, if you want it

On Tier 2, M-Pesa premium collection and automated index-triggered payouts.

​
How it works

​
Where our responsibility ends

We are explicit about this because it is the product. On Tier 1 MicroCrop determines whether the trigger fired and issues the signed determination and evidence package. MicroCrop does not collect premium, does not hold your capital, does not pay the farmer, and does not verify that you did. The obligation to the farmer is yours, and the API says so on every response. See Service tiers.

​
Before you start

Integration is gated on KYB verification (including your insurance regulator’s operating licence) and on underwriting capacity recorded with MicroCrop. Read Requirements first, then follow the Quickstart.
Base URL: all endpoints live under https://app.microcrop.app/api. Authentication uses an organization API key in the x-api-key header — see Authentication.