Sahkarmi is a tested rule layer for a merchant-desk AI agent. It is a hackathon prototype on a simulated back office, and the ask is simple: a shadow run on real cases that acts on nothing.
Recordings of the real agent on a simulated back office. Left: the shop's phone. Right: what Sahkarmi did.
Hinglish demo
Recorded on the prototype, with what works, what does not, and what we are asking for.
The problem
"Kirana sales don't have invoices, so there's nothing to upload."
Who else is doing this
Paytm owns the shops, the data and the reach, and it could build all of this. What we bring is a stated rule, tested in the open: code decides, and a case closes only after a system check.
| What they show in public | Paytm | BharatPe | Razorpay | Sahkarmi |
|---|
From public sources, Oct 2026. "Not shown" means not found in public, not that it does not exist. Sahkarmi's column is a prototype on simulated systems.
The four questions
What is not real yet
Our own audit found four holes on 31 Oct: one Confirm tap could pay repeated refunds, a reworded reason skipped the once-only rule, "ok thanks" counted as consent, and a case could close with a problem still open. Those four cases no longer run, and each has a test. Tying consent to a specific offer is still open.