Baret runs every Monad transaction without sending it, before you sign. It checks the result against your rules. Then it tells you what it found, in plain words. The same check covers your AI agents.
Three layers around one signature: before you sign, while a permission stays open, and after it is used. Each layer works on its own.
Reads it
Before your wallet signs, Baret simulates the transaction against live Monad state, reading the chain over Alchemy's Monad RPC. Nine detectors read the result. Reputation comes from Nansen and from threat feeds that Chainlink CRE writes on-chain.
Caps it
Some signatures leave a permission behind, like a site allowed to spend your tokens next year. Baret keeps every one in a single list: who can spend, how much, and a Revoke button.
Watches it
Baret keeps watching after you sign. You get an alert when an allowance is used or funds leave without your signature.
9
detectors read every transaction
25
rules you can switch on, off or tune
6
fake sites with real attacks to try
800 ms
until Monad makes a transaction final
No user counts and no totals. Baret is on testnet, so it counts only what it ships.
Each site looks like a real product and builds a real transaction on Monad testnet. Connect any wallet, press the main button, and read the verdict before anything is signed.
Let an agent pay per question. Watch the cap hold.
Swap tokens. See where the output really lands.
Mint one item. See what else the button grants.
Stake for yield. See who has verified the pool.
Claim a free airdrop. See what you are really signing.
Buy into a token sale. See who still holds the controls.
These sites are fakes built for the showcase. They run on testnet and cannot touch real money.
Open the showcaseA check with two answers has to round. Round down, and a contract nobody verified passes as fine. Round up, and every swap looks alarming until you stop reading. Baret has a third answer. You can sign, and the reason comes first.
Checked: simulation · approvals · recipient
If signed
A site could spend all of your USDC, today or next year.
This lets this site's contract take all of your USDC, including any you receive later, until you revoke it.
An example request with sample data, not a live check.
No rule was broken and no check found a problem. You still see exactly what changes before you sign.
No rule was broken, but a check found something worth a look. For example, a contract nobody verified, a brand-new wallet, or a fee far above the need.
A rule you set stopped it. Baret names the rule, not a score. In the extension, signing anyway takes a separate press‑and‑hold, and it is logged. The web wallet never signs a blocked request.
The fourth verdict: Can't reach Baret
x402 lets an AI agent pay for an API by itself, in small payments. It is stateless on purpose: no running total, no cap, no way to revoke a key. Baret keeps the memory the protocol leaves out. Your agent gets a leash, a budget and a kill switch.
The agent's own wallet comes from Dynamic, and the vault owner authorises it with their Mera passkey. Per-payment and daily caps live on‑chain in your PaymentGuard vault.
Caps for each merchant, per payment, per hour and per day. Every payment counts against a real number. The one that crosses it does not go out.
A sample run: an agent asks Scrybe 20 questions at 2 USDC each.
10 of 20 paid. This payment of 2 USDC would bring the last 24 hours to 22 USDC. Your daily cap is 20 USDC.
A sample run with sample data, not a live payment.
Baret checks the token contract against your list of allowed assets. A look-alike fails, even with a perfect name.
The agent's key can only pay from your PaymentGuard vault, inside your caps. Revoke it in one transaction and every later payment from it fails on-chain.
Open the showcase and press Claim on a fake airdrop. Read what Baret finds before anything is signed.
MIT licenceSourceNot audited yetMonad testnet onlyFails closed
