Who Veto is, and why.
A short, honest version. Operated by a small team out of Investech Global LLC.
The thesis
Every agent demo I'd seen in late 2025 ended with the same caveat: "we wouldn't actually let it touch real money." That's not a feature; that's an admission. Either the agent is real and the money is fake, or the money is real and the agent is sandbox-only. The third option — a real agent, real money, and a contract you can audit — wasn't on offer.
Veto is the third option. We're the boundary between an AI agent and whatever it's about to spend on. We don't try to be the wallet, the payment rail, or the agent framework — those layers already have good providers. We're the policy + risk + receipts layer that sits across all of them. Our job is to be wrong as rarely as possible, and to leave behind verifiable proof when we are.
Three things we believe
The boundary is a contract, not a hope. Cooperative enforcement (the agent asks nicely; the policy layer answers) is the default in this market. We ship cooperative mode AND on-chain hard-stop: a smart contract that refuses replays even if our API is down. The cooperative path is the fast path; the chain path is the can't-be-talked-out-of-it path.
Receipts you can verify without us. Every Veto decision
ships with an Ed25519-signed JWT. The public key is at
/.well-known/jwks.json.
Your auditor, your counterparty, or just your future self can verify
a decision with the open-source
mandate-verifier
package — Veto doesn't have to be online for you to trust the proof.
Build in public or don't build at all. The CLI, the SDK, the policy schema, the contracts, the verifier, our own internal policies — all open-source on github.com/veto-protocol. Most launch posts are vapor. We post commits.
Who runs it
Veto is operated by Investech Global LLC, a Delaware LLC. The product team is small — currently myself plus contributors — so support is fast and decisions don't take three weeks. If you email tomer@veto-ai.com a real person reads it within one business day.
What's next
We're in the v1 launch window for x402 and Stripe MPP integration. Next up: Solana ports, AP2 mandate composition, and the Claude Code plugin install path going through the marketplace. Roadmap moves with users — tell us what you need.
If you're shipping agents that move money — on x402, on cards, on-chain, anywhere — drop a line. v1 cuts in days.
— Tomer Meirovich, founder · tomer@veto-ai.com