A small proxy that runs on your own computer, between your AI agents and the internet. It pays automatically with stablecoin under the limit you set — free and open source. Add-ons let it cryptographically prove which agent made a payment, and automatically catch sensitive data before it ever leaves your machine.
A compliance team. A bank partnership. Or time to build all of this yourself.
Minimums and manual approval hold up for one payment. They don't clear a $0.02 charge a thousand times an hour, and they weren't built to check who's actually asking.
Identity checks, spend policy, and data-loss prevention are the right size once you're big. At two people, it's a sales call before your first payment clears.
Wire a payment SDK to your agent yourself, and your first spend limit — and your first accidental data leak — is whichever bug you haven't hit yet.
Point your agent's HTTP client at it. No SDK, no rewritten code.
Runs quietly on your own computer in the background. No account needed to start, and we never hold your money or see your traffic.
A spending cap is on by default the moment you create an agent. Stablecoin payments under the limit clear automatically. Nothing over it does — free, open source, no account required.
Two add-ons plug into the same proxy: one signs every payment so you can prove which agent made it; the other catches emails, card numbers, and API keys before they leave the machine. · paid add-ons
Each one plugs into the same request path. Turn on only what you need.
Your agent's requests get paid automatically with stablecoin whenever a site asks for payment — never over the budget you set, per agent.
Every agent gets its own cryptographic identity. Payments are signed with it, so you can prove which specific agent made which payment — and shut one off instantly if it's ever compromised.
Outbound requests are checked for sensitive data before they're sent anywhere — emails, phone numbers, card numbers, and common API-key formats are caught automatically.
Most people never open the settings file below. It's there if you want it.
A plain YAML file per agent. This one has all three pieces turned on, stacked so identity is checked first, then privacy, then the payment itself goes out.
A local web page — not a cloud service — showing spend, who signed what, and what got blocked.
| Agent | Today | Signed by | Status |
|---|---|---|---|
| pricing-bot | $0.86 / $5.00 | did:key:z6Mk…7Fd | allowed |
| pricing-bot | — | did:key:z6Mk…7Fd | redacted · email |
| research-agent | $0.14 / $2.00 | did:key:z6Mv…2Aq | allowed |
| research-agent | — | unsigned | blocked · no identity |
Local-first by design — self-hosted, free at the core. That doesn't change as it grows.
It lives on your own machine as a background process. Nothing routes through our servers by default.
Payments move directly between your agent and whoever it's paying — signed and forwarded, never custodied by us.
Wallet and identity keys are encrypted at rest with AES-256-GCM + scrypt, on your disk — never sent anywhere to unlock.
The proxy and the free payment engine are Apache-2.0. Every payment lands in a local log you can query yourself.
One command to install. No account required to try it.
Building from source works today too: go install github.com/agentOnRails/agent-on-rails/cmd/aor@latest