Spending rules
for teams and
their AI agents.
The agent proposes. Only the contract authorizes. One dollar account where every person and every AI agent gets its own limits, enforced on Monad.
Example: a team account owned by Alex. Marcus, a person, and two AI agents, Ronnie and Scout, each spend within their own limits at an approved service; a payment over a limit waits for Alex to approve it.
Built on Testnet. Test funds only.
LatestAgents can now pay on a scheduleHow it works
Rules before
money moves
From the first instruction to the final receipt, Nuntio keeps the rules visible and the next step clear.
- 01
An allowance for every spender
Give each person or assistant an allowance, a per-payment cap, and approved services.
- 02
Only approved services
The model names a service. The registry resolves its payee, not the assistant.
- 03
Over the limit, the owner decides
An exception stops for your review. Approving it and moving the money are separate steps.
Core capabilities
One account for
agents and people
Agents
Assistants work
inside the rulesGive an AI assistant its own allowance, cap and approved services. It can propose a payment, or pay on a schedule by itself, and the contract still checks every one.
People
One shared
accountKeep your team’s test AUSD in one place. See the balance without switching between wallets.
Control
An exception is
your decisionWhen a payment exceeds its rules, it stops. Review the request, then explicitly complete an approved payment.
Receipts
A receipt for
every paymentKnow what is waiting, approved, or settled. A payment is confirmed only when a receipt exists.
Monad
Settled on
MonadA payment confirms in under a second and costs a fraction of a cent, so a small charge is worth sending. Live on testnet with test AUSD.
Every spender, one policy.
Settled on Monad.
The policy layer
Read the security modelThe payment rail is solved. The policy layer above it is not. Nuntio lets a human give people and AI agents a budget the contract enforces, so the assistant proposes and only the contract authorizes.
Limits before payments
The contract checks the allowance, service, expiry, and pause status.
Known services only
The model names a service. The registry resolves its payee, not the assistant.
Access you can take back
Pause a spender or revoke permission. New payments must pass the updated rules.
Testnet prototype · Not independently audited · Server-admin owner actions are disclosed in our trust model.
FAQ
Got more questions?
See the demo01What is Nuntio?
Nuntio is a shared stablecoin spending account for teams and AI assistants. Each spender has a policy, and the onchain account checks that policy before money moves.
02Can I use real money?
No. This hackathon build runs on Monad testnet using test AUSD. Do not send real funds. The transactions are onchain, but the balances are test funds.
03Can an assistant spend without limits?
No. The assistant proposes a payment to a registered service. The account enforces the spender’s allowance, per-payment cap, approved services, frequency, expiry, and pause status.
04What happens when a payment is blocked?
No money moves. Where an exception is eligible, the spender can submit a separate approval request. The owner reviews it, and settlement requires another explicit transaction.
05Do I need a wallet extension?
You can sign in with Google or email through Privy. An embedded wallet handles the signing flow. Gas sponsorship is still being validated; this is not a promise of gas-free payments.
06Is Nuntio independently audited?
No. The prototype has automated tests and testnet payment evidence, but it has not had an independent security audit. The demo uses a disclosed server-side admin for owner actions. Read Our approach for the trust model.