Priced by verifications, not seats.
Three tiers, calibrated to the shape of the book being verified. Larger institutions and cooperative networks talk to us directly - a single monthly volume, one integration model, one contract.
For a single branch, a district cooperative, or a pilot deployment inside a larger institution.
- Land record digitization
- Ownership verification
- Crop history tracking
- Audit-quality provenance on every field
For growing NBFCs, mid-size cooperative networks, and regional bank branches scaling agri-lending.
- Everything in Starter
- Loan eligibility scoring
- Portfolio risk analytics
- LOS integration through signed JSON API
For public sector banks, national NBFCs, and state-level cooperative federations.
- Everything in Growth
- Custom risk models on your book
- Dedicated onboarding and named support
- Data residency and audit review windows
What each tier unlocks, capability by capability.
No hidden features, no upsell pop-ups. If it is on the tier, it is in the API and in the workspace on day one.
| Capability | Starter | Growth | Enterprise |
|---|---|---|---|
| Land record digitization | |||
| Ownership verification | |||
| Crop history tracking | |||
| Loan eligibility scoring | - | ||
| Portfolio risk analytics | - | ||
| Custom risk models | - | - | |
| Dedicated onboarding | - | - |
Questions we hear from credit teams.
The short answers to the questions that come up on most first calls with a lender.
How does regional data coverage actually work?
Registry coverage varies by state and district. The verification result always states the source, the freshness, and the confidence. Where a state or district is not covered, the record says so and offers a downgraded verification path.
How does the platform integrate with an existing LOS?
Verification returns a signed JSON object your loan origination system can consume, with provenance for every field. Most integrations sit as an origination-time verification step, before the file reaches underwriting.
Are contracts monthly, annual, or usage-based?
Starter and Growth are typically annual with a monthly verification volume commitment. Enterprise is negotiated per contract - volume, data residency, and support windows are all discussed on the first call.
Who owns the verified parcel records?
The institution owns the verified records for its own book. Aggregate, anonymised patterns may be used to improve regional model calibration - the contract states this explicitly and the institution controls the opt-in.