Open source · v0.1 alpha
AI agents can spend money. Railguard makes sure they spend it right.
A safety layer that checks every agent payment before it is signed, and proves what really happened after. Your wallet and keys stay yours.
Pay 7,500 USDC
to 0x9f3…c41 · not on the allow list
- Recipient allowedNO
- Within budget (5,000)NO
- Wallet asked to signNEVER
What it stops
Three mistakes that cost real money.
Agents retry, race each other, and follow bad instructions. Here is what changes with Railguard in the path.
Without Railguard
- The agent sends a 1,000 USDC payout.
- The network is slow, so the request times out.
- The agent retries. The first payment had gone through.
Paid 2,000 USDC for one invoice.
With Railguard
- Every payment gets one id before it leaves.
- After a timeout, the state is UNKNOWN, not failed.
- Railguard checks the chain, sees it paid, and stops the retry.
Paid exactly once.
How it works
Check. Watch. Prove.
Railguard sits between your agent and your wallet. It never holds the money.
Check
Your rules run before the wallet signs: allowed recipients, budgets, approvals. Money is reserved so two agents cannot spend it twice.
Watch
After sending, Railguard tracks the chain. If the answer is lost, the payment is UNKNOWN until it is checked, never guessed.
Prove
Every payment ends with a tamper-evident receipt: what was asked, what was allowed, and what the chain shows.
Proof, not promises
Every claim links to a transaction you can open.
Testnet runs, committed evidence files, no sign-in needed.
0.01 USDC, settlement verified
Railguard checked the intent, watched the transfer and matched it on chain.
Recorded 30 Sep 2026
Policy contract, 5 attacks rejected
Budgets and intent rules enforced on chain: replays, wrong recipients and overspend fail.
Recorded 23 Oct 2026
1 USDC transfer matched
Railguard read the receipt logs and matched token, sender, recipient and amount.
Recorded 4 Oct 2026
3 agents under on-chain limits
An over-cap purchase was refused, limits were re-approved, and a lost payout paid once.
Recorded 23 Oct 2026
Use it your way
For the people who build agents and the people who pay for them.
Developers
Wrap a payment in one call, or give your agent Railguard as MCP tools in Cursor or Claude.
const result = await check(rg, intent) if (result.decision === "ALLOW") await rg.execute(result.intent.id)
Finance and ops teams
Set limits per agent, approve changes, and get a receipt for every payment.
- Spending limitsper agent, per payment
- Approvalsa person signs off on new limits
- Receiptsre-checkable, tamper-evident
Open source
Read every line that touches the money.
- LicenseApache-2.0
- Checks on every pushlint, unit and lifecycle tests, builds
- ContractsEVM hook (Arbitrum) · Soroban policy (Stellar)
- InterfacesTypeScript SDK · CLI · MCP · REST API
Built by
Prasanth Kuna
Railguard is my open-source personal project. I am a payments and backend engineer, and I built it to show that agent payments can be safe by default.
Give agents authority. Not unlimited money.
See it block a bad payment in under a minute.