I’m building Timbro around a question I haven’t validated yet: when an AI agent buys data or work from an unfamiliar provider, what happens if the delivery is wrong or never arrives?
I built a browser sandbox where you can play both sides of a $250 dataset purchase. You can fund the deal, deliver the dataset, approve it, or dispute it. Every dollar is simulated—there’s no account or real payment involved.
I’d especially like to hear from people building agents that already purchase data, API access, or services:
How do you handle payment approval and failed delivery today? Would a flow like this be useful in your project, or is the problem still too far ahead of actual usage?
You can try the sandbox here: https://timbro.tech/sandbox/
Candid feedback is welcome, including reasons you wouldn’t use it.
I’d separate spending approval from delivery acceptance. In my own agent workflows, the agent can prepare the purchase, but a human or a budget policy approves the spend; after that I only close the job when a provider receipt, webhook, or verified output matches the order. If delivery is silent or ambiguous, I keep it in submitted/unresolved instead of letting the agent mark it done.
That separation makes a lot of sense. Preparing a purchase, authorizing the spend, and accepting delivery should be distinct steps. I also like your point about keeping ambiguous delivery unresolved.
In your workflows, what evidence would you trust enough to release payment automatically—if any? Or would you always want a human to approve that final step?
This is great work — reminds me of some of the calls I've had to make building Xstream4K. What would you do differently if you started over?
Have conversations with agent builders revealed actual recurring purchases from unfamiliar providers, or is the payment-and-dispute problem still mostly a future workflow?
Delivery acceptance is the part I’d make explicit: payment authorization and completion should be separate state transitions, with a timeout and an evidence requirement for each. That gives the agent a safe way to retry or escalate without silently treating an unverified response as a successful purchase.