Skip to content
Work

I build the systems that let software act in the real world.

This is the short map of Mattia Ciuni's work. The common thread is not a job title or a list of technologies. It is the point where software stops being a tool you click and starts acting on someone's behalf. First that meant helping an agent navigate the web. Now it means giving an agent controlled, accountable spending power.

Payle

Current work

Payle is the money layer for AI agents. I am building the authorization and payments infrastructure that makes autonomous spending safe enough to use: scoped capabilities, per-agent and per-task limits, merchant rules, approval thresholds, idempotency, revocation and receipts that explain what happened. The goal is not to hand a model an unrestricted wallet. The goal is controlled delegation: a person or company defines the boundaries once, an agent works inside them, and every decision can be inspected afterwards.

This work sits across AI agents, agentic commerce, fintech infrastructure, risk, payments and software reliability. The difficult questions are deliberately practical. What happens when two identical requests arrive together? What does a merchant need to verify? How should a failed risk service behave? How can an operator revoke authority immediately? I write the answers as I discover them in Thoughts and Notes, and I publish useful corrections from other people in Feedback.

Visit Payle →

Celeste

Earlier work

Before Payle, I built Celeste, an AI browser. It could open pages, follow instructions, research, compare options and complete workflows. The important lesson was not that the agent could navigate a browser. It was that the last ten percent of an apparently finished task exposed a completely different infrastructure problem. The agent could do the thinking and the work, then it stopped at the credit card form because the financial system assumed that every actor was a human with a hand, a wallet and a phone.

That experience became the starting point for Payle. It connected a product question about browsers to a larger question about authority, liability and trust. Celeste is part of the context for the current work, not a separate keyword page or a claim that the two products are the same.

The topics underneath

The projects are connected by a set of questions I keep returning to: how agents receive permissions, how a payment system remains deterministic under concurrency, how trust can be represented in a receipt, and how a founder can build in public without turning the work into theatre. These are the subjects behind the site, and they are more useful than a page of invented expertise.