Pinned Tweet
Agents act. Levee decides.
Approve what your AI agent can buy once, with a passkey. Every payment is checked against it before it goes through: approved, declined, or sent to you.
Sandbox opening soon. Follow along.
1
1
31
A question I keep asking founders who run agents with a company card:
If your agent spent $3,800 on GPU credits over the weekend, and finance asked on Monday who approved it, what would you show them?
Most answers so far are some version of "the agent had access." A few say "it's in our logs."
Access isn't approval though. And the logs were written by the same system that made the purchase, so they prove what happened, not that it was allowed.
With employees this is solved and nobody thinks about it. There's an expense policy, someone signs off, the receipt goes in a folder. When an auditor asks, you pull the folder.
Agents skip all of that. They get a key and a card and we hope.
At @levee_dev we start from the folder. Before the agent spends anything, a person signs off on what it can buy, from where, how much and until when, with a passkey on their phone. Each payment gets checked against that sign-off before the money moves. Every yes and every no goes into a record you can check yourself, offline, without having to trust us.
So the Monday answer becomes: this is what I approved, this is the payment, they match, and the record hasn't been touched.
I think this is where agent payments get stuck inside real companies. Not at "can the agent pay" but at "can we prove it was allowed to."
Curious how teams are handling this today. Are you approving agent spend at all, or just capping the card and hoping?

