Agent payments · live on Solana
Orvane turns spending rules into on-chain mandates. Set a per-payment cap, a rolling 24-hour budget and an approved recipient list. Every payment your agent proposes is checked against the mandate before you sign, and settles on Solana in under a second.
How it works
Name your agent, set its caps and approve recipients. The mandate is written to Solana as a signed memo from your wallet, so anyone can verify it.
Your agent describes the payment in plain language. Orvane parses it into an exact amount, recipient and reason.
Six deterministic checks run against the mandate and your real on-chain spend history. Anything outside policy is blocked before it reaches your wallet.
Approved payments are one transfer plus a tagged memo. You sign once, and the receipt is permanent and public.
Use cases
Software that spends money needs rules that software cannot rewrite. These are the workflows Orvane is designed for.
Autonomous agents increasingly buy API calls, datasets and GPU time on their own. Orvane lets them pay vendors you pre-approve, in small bounded amounts, without ever holding an unlimited wallet.
Give an ops agent a small daily allowance for recurring spend while the main treasury stays untouched. Raise or lower the allowance by publishing a new mandate.
Automate bounties and invoices to a fixed roster of contributors. Each payment is capped, tagged with its reason and recorded on-chain the moment it settles.
Every mandate and payment is a public Solana record. Finance and compliance get a tamper-proof receipt trail, and anyone can verify the limits that were in force.
How to use
Use Phantom, Solflare or any Wallet Standard wallet. Orvane never sees your keys. It only asks your wallet to sign.
Connect your wallet and keep the network on Devnet while you learn. Tap "Get 1 devnet SOL" for free test funds, or use faucet.solana.com if the faucet is busy.
Name the agent, set the per-payment cap and the 24-hour budget, then paste up to five approved recipient addresses. One signature writes the mandate to Solana.
Atlas · 0.1 SOL per payment · 0.5 SOL per dayIn the payment desk, describe the payment in plain language. Orvane extracts the amount, recipient and reason, then runs six guardrail checks against your mandate and real on-chain spend.
Pay 0.05 SOL to 7xKX…gAsU for GPU hoursApproved payments show a green checklist. Sign once in your wallet, and the transfer settles with a tagged memo. Open the receipt in Solana Explorer from the activity feed. Blocked payments never reach your wallet.
On-chain anatomy
Mandate · Memo program
orvane:v1:mandate:{
"n": "Atlas",
"t": 0.1, // per-payment cap
"d": 0.5, // 24h budget
"a": ["7xKX…", "9wFh…"]
}Payment · Transfer + Memo
SystemProgram.transfer(
owner → vendor, 0.05 SOL
)
orvane:v1:pay:{
"m": "5Kq2xV…", // mandate ref
"r": "GPU hours"
}The console reads your wallet history straight from Solana RPC, so your active mandate and rolling 24-hour spend are always reconstructed from verifiable records. Policy checks run in the Orvane client before you sign; the on-chain record makes every limit and every payment independently auditable.
FAQ
No. Orvane is non-custodial. Every transaction is built in your browser and signed by your own wallet.
On Solana, as a signed memo from your wallet. There is no database. The console reconstructs your active mandate and 24-hour spend straight from RPC.
You publish a new one. The most recent mandate from your wallet always wins, and the history of older mandates stays visible on-chain.
Solana Devnet and Mainnet. Start on Devnet. Mainnet uses real funds and public RPC endpoints may rate-limit.
A sentence containing an amount in SOL and a recipient address, optionally followed by "for" and a reason. For example: Pay 0.02 SOL to <address> for API credits.
Connect a wallet, publish a mandate and send your first guarded payment on devnet in a couple of minutes.
Open the console