BUDGENT
Budget for your agent,
not keys to your wallet.
A private key gives an agent all your funds. Budgent gives it a budget the chain enforces — per-tx caps, daily limits, a recipient allowlist, an owner co-sign threshold. Break a rule and the network reverts the transfer, not us.
- [ On-chain enforced ]
- [ REST, not x402 ]
- [ Context-tagged ]
[ ] HOW IT WORKS
From a funded vault to autonomous, bounded spend — in four steps.
-
01
Fund the vault
Top up a Vault PDA — a program-derived account on Solana with no private key. Your master authority never leaves your wallet.
-
02
Write the budget
Set a per-tx cap, a daily limit, a recipient allowlist, and a co-sign threshold. The agent gets a delegate key — never your keys.
-
03
The agent pays
Explicit REST calls: create intent → policy check → on-chain → receipt. The program checks every rule; break one and the transfer is reverted.
-
04
You read it by context
Every payment is tagged with domain, resource, and task — spend grouped by where it went. Revoke the delegate any time, instantly.
[ ] THE AUTHORITY CONSOLE
Set a budget, run the agent, and watch the chain enforce every rule — live, in your browser. Tighten the budget, re-run the same task, and watch strictly more transfers get reverted.
// You are the OWNER (master authority). Press Run — the program checks every rule before money moves.
01 · WRITE THE BUDGET
02 · AGENT RUN
DAILY ALLOWANCE
CO-SIGN QUEUE — awaiting owner
[ ] WHAT THE CHAIN ENFORCES
The rules live in an Anchor program — not on our server.
Off-chain code can't spend more than the program permits. Each rule maps to a concrete on-chain consequence — checked on every transfer, in consensus.
- delegate revokedREVERTED
- recipient blocklisted / off-allowlistREVERTED
- over per-transaction limitREVERTED
- over daily limitREVERTED
- over vault balanceREVERTED
- at / over co-sign thresholdHELD for owner