AI-agent pay links it can create but can't spend

Let AI generate payment links with spend rights locked down—receivable, not spendable

Problem

The biggest fear when letting an AI agent transact is that it will spend or move the money itself; existing crypto payment tools give the agent full wallet permissions by default, which ordinary users neither trust nor can audit. Builders are already exploring agent-created payments that the agent cannot spend, showing the pain is real.

Solution

A small tool for restricted payment links: the agent can only create a receive link or one-time payment request for a fixed amount; funds land in an escrow address and only a human can release them. Every step is logged, and links can expire or carry limits.

Users

Indie developers and small Web3 teams experimenting with AI-agent transactions or collections

MVP

Generate restricted receive/pay links; escrow address with human release toggle; link expiry and limits; operation log; simple web page to view and release

Revenue

Small per-transaction fee, or monthly team subscription

Why now

Agent payments are moving from concept to experiment, but loss-of-control fear is the main blocker; a narrow 'generate link + human release' tool ships in a week or two and avoids licensing by keeping humans in the loop