Your AI agent can be fooled.
Your treasury can't.

Agent Guard sits between AI agents and money. Hard limits and allowlists first, an AI fraud screener second, a human for anything unusual, and settlement to any chain through NEAR Intents. The agent never holds a key.

0
attacks blocked
0
held for a human
$0
paid safely

1 · Agent inbox

2 · AI agent (naive on purpose)

Pick an email. The accounts-payable agent reads it and pays whatever it asks for, exactly like a real agent that got prompt-injected.

3 · Agent Guard

Every payment the agent attempts lands here first: policy, AI screener, verdict, then settlement.

How the Guard decides

01 · POLICY
Deterministic rules

Per-payment cap, daily budget, rate limit, chain and token allowlist, payee allowlist, denylist, "known vendor at a new address" check. No prompt can change them.

02 · AI SCREENER
Reads the context as data

Gemini scores prompt injection, urgency, secrecy, impersonation and payee changes. It can only make a decision stricter. If it is down, the Guard fails closed.

03 · HUMAN
Hold, don't guess

Unknown payees and big amounts wait for the owner in the console or Telegram, and expire if nobody decides.

04 · SETTLE
NEAR Intents

Approved payments leave the treasury as USDC on NEAR. Other chains route through 1Click, with a fee ceiling. Every step goes into a hash-chained audit log.

Plug in any agent

Why not just trust the agent?

An LLM that reads emails, invoices and web pages will eventually read one written by an attacker. Prompt-level rules like "never send more than $25" are suggestions to a model; to the Guard they are code. The agent gets an API key that can only ask for a payment, and the keys to the money stay with the Guard.

Try it: write your own email in the inbox and try to make the agent pay you. Every attempt is in the audit log.