One policy, every wallet. Cross-rail spend governance, approvals, and audit for AI agents.
Your agents can spend from many wallets. AgentVeins governs them with one policy — and proves every payment.
npm install @agentveins/coreagent-07team-policy.json
$ agent run --policy team-policy.json ✓ pay api.weather.com 0.05 USDC settled (daily: 24.35/25.00) ✓ pay api.weather.com 0.05 USDC settled (daily: 24.40/25.00) ✓ pay data.chainfeed.xyz 0.55 USDC settled (daily: 24.95/25.00) ✗ pay api.weather.com 0.10 USDC BLOCKED budget.daily exceeded → violation logged · audit #a41f9 · owner notified $ veins freeze agent-07 ✓ kill switch active — all wallets
Every payment answers five questions before money moves
Corporate card controls, for AI agents.
| Check | Question it answers |
|---|---|
| Allowlist | Is this vendor approved — on one list covering every rail? |
| Budget | Is it within per-payment / daily / periodic limits on aggregate spend? |
| Approval | Does this payment need a human sign-off first? |
| Velocity | Is this normal behavior, or a runaway loop? |
| Kill switch | Is this agent still authorized — across every wallet at once? |
Payments that pass proceed untouched — the agent never notices. Payments that fail return a structured violation the agent can handle gracefully. Every attempt on every rail, allowed or blocked, lands in one tamper-evident audit log.
Why now
57.4%of HTTP requests are bot-originatedCloudflare Radar · June 2026
~160Mx402 transactions settled to datex402 · to date
~16.7%of enterprise AI budgets go to agent security and governanceIDC
The rails exist. The cross-rail control layer doesn't.
What AgentVeins is not
- Not a wallet — it never holds funds
- Not a payment rail — x402/Solana/Base move the money
- Not an agent framework — bring your own agent
Common questions
- Does AgentVeins hold my funds?
- No. It never holds funds and it never moves them — x402, Solana and Base do that. AgentVeins sits above your agents' wallets and decides whether a payment is allowed, before the money moves.
- Some wallets already have spending caps. Where does AgentVeins fit?
- Wallet providers are shipping allowances, allowlists and caps of their own, which validates the whole category. Those controls work per wallet. A real deployment holds several wallets across several rails, so aggregate spend, one org-wide policy, and a single audit trail all sit a layer above any individual wallet. Wallets with built-in caps are rails AgentVeins governs through adapters — the way a password manager isn't competing with each website's login form.
- Which chains and rails does it support?
- Solana first, with the devnet adapter live. Base and Cloudflare Wallets adapters come next. The policy engine has zero chain dependency, so the same policy applies to each new rail as its adapter lands.
- What happens to my agent when a payment is blocked?
- Blocked is not thrown. The call returns a structured violation the agent can handle gracefully — retrying a cheaper vendor, or escalating to a human — and the attempt lands in the audit log with the reason it was refused.
- How long does integration take?
- The target is under 10 minutes from npm install to your first governed payment. You wrap your agent's payment path, and that is the only integration point.