AI agents can think. They still can't pay.
So I built Loki: an MCP server that lets your agents send M-Pesa payments and use virtual cards, inside the caps, budgets and allowlists you set.
Built on @SafaricomPLC Daraja. Sandbox-tested. Waitlist below.
#MPesa#AIagents#MCP
Agents will retry. Networks fail, models loop. If a payment tool isn't idempotent, a retry becomes a double charge. With Loki (sandbox-tested MCP payment gateway) every call carries a key, and per-payment caps plus monthly budgets return hard denials, not warnings. #MCP
@YogeshBaks53995 Per-request keys are right, but also persist the key with the result, not just a seen-set, so a retry after a timeout returns the original outcome. For reconciliation, treat Stripe webhooks as source of truth and keep the stream's ledger entries pending until confirmed.
I'm less interested in which model wins the leaderboard.
I'm interested in where judgment still lives when the model is in the loop.
If your system can't say "I don't know," it will confidently ship the wrong answer.
@rY3kop The "fix what you broke while hardening" loop is real. Detection software that survives its own false positives is the boring half of shipping security tools.
@ClementDelangue Open weights that run well on Mac Studios matter more than the launch headline. Local-capable models change what you can ship without a cloud round-trip on every call.
@ThePrimeagen Dotfiles as agent setup docs is underrated. The useful part is encoding the non-obvious machine preferences once so every new session starts from the same baseline instead of re-explaining it.
@sparrowbrainz Solid stack — SELECT-only user plus a single-statement parse. That puts the hard limit in the DB and the parser, not in a prompt the model can talk around.
@__ciox__@engimeets That double-tax gap is the real cost of the Delaware path from Kenya. Worth modeling payouts and KRA exposure early, before the first US invoice, so the entity choice still pencils once both sides collect.
@CharlesHNR_@make_hq Nice flow. I would add a fallback branch so leads still get the instant alert if the OpenAI step errors or times out. Speed-to-lead breaks quietly when one hop in the chain fails.
@levelsio@Microsoft@XBOX@satyanadella@asha_shar Fan ports made out of enthusiasm are free marketing for the original games. Embracing them keeps the community building on the brand, and that goodwill is worth far more than the takedowns would protect.
@levelsio The uncomfortable part is that customers never agreed to their workflow data being resold. Once that is a known exit path, data-processing terms and deletion rights become a real buying criterion for SaaS.
@WOkparaji74619 Good result on dim light. Since scores only count frames where the hand was detected, I would also log the detection rate per condition next to accuracy. That shows whether lighting hurts the detector or the classifier.
@rileybrown Voice-first while walking is a real workflow shift. The hard part is keeping the agent scoped so a yap doesn't spawn five half-finished sessions.
@theo Internal token spend as a product feedback loop is underrated. If your own agents can't burn that much usefully, the product surface probably isn't agent-shaped yet.