A prefunded petty-cash vault for pay-per-request agents, with hard caps and receipts you can reconcile.
Spending limits are enforced before payment, at the vault, not just reported afterward. The owner gets accounting-grade receipts, which raw payment rails do not give them.
- Mint authority revokedpass
- Freeze authority revokedpass
- Top 10 hold 23.2%check
- Liquidity lockedcheck
- Metadata immutablepass
Score
Share
One link with the full report.
Petty, feature by feature.
Built for developers and teams running research, scraping or tool-using agents that buy data and compute per request, and the people who answer for their bills.
Policy editor: caps per agent, per service domain and per day, plus an allowlist of payees
PlannedDrop-in fetch middleware (npm package) that handles 402 responses, checks policy and pays
PlannedAnomaly pause: repeated failed payments, price jumps above the quoted amount, or first-time payees stop the agent until
PlannedReceipts ledger with CSV export tagged by agent, service and date
PlannedVault creation on Solana with a single signed deposit and withdraw back to the owner at any time.
Paste an address and get a plain report in about a second. Each line says what was checked and what it means.
Planned- Mint authority revokedpass
- Freeze authority revokedpass
- Top 10 hold 23.2%check
- Liquidity lockedcheck
- Metadata immutablepass
Policy editor: caps per agent, per service domain and per day, plus an allowlist of payees.
Line several tokens up side by side and sort by what matters to you.
PlannedCompare
| Token | Score | Top 10 | Liquidity |
|---|---|---|---|
| RAMO | 48 | 56.4% | locked |
| ZUFA | 63 | 54.2% | locked |
| RAZU | 79 | 33.6% | unlocked |
| NESA | 72 | 67.0% | locked |
| DOQU | 93 | 16.8% | unlocked |
Spending limits are enforced before payment, at the vault, not just reported afterward. The owner gets accounting-grade receipts, which raw payment rails do not give them.
3 steps from start to first result.
Open by default.
Every screen reads from the same model. Live parts read public onchain data; nothing ever asks your wallet to sign.
Read the docs{
"product": "Petty",
"network": "solana",
"features": [
{
"name": "Vault creation on Solana with a single signed de",
"status": "planned"
},
{
"name": "Policy editor: caps per agent, per service domai",
"status": "planned"
},
{
"name": "Drop-in fetch middleware (npm package) that hand",
"status": "planned"
},
{
"name": "Anomaly pause: repeated failed payments, price j",
"status": "planned"
}
]
}What works today.
Live features work today. Planned ones are next on the roadmap, in this order.
Questions.
Short answers. The docs have the rest.
What is Petty?
A prefunded petty-cash vault for pay-per-request agents, with hard caps and receipts you can reconcile. Spending limits are enforced before payment, at the vault, not just reported afterward. The owner gets accounting-grade receipts, which raw payment rails do not give them.
What works today?
Petty is in development. Every feature is on the status list with what ships next, and the app opens in a sample workspace so you can see how it will work.
Do I need a wallet?
No. You can explore without one. Connecting a Solana wallet only shares your public address so Petty can read your balances; it never asks you to sign a transaction.
Who is it for?
Developers and teams running research, scraping or tool-using agents that buy data and compute per request, and the people who answer for their bills.
Vault creation on Solana with a single signed deposit and withdraw back to the owner at any time.
A prefunded petty-cash vault for pay-per-request agents, with hard caps and receipts you can reconcile.