INTENTGUARD · AI PAYMENT SECURITY

Compromised agent.
Protected money.

Let your agent make the request.
Let NEAR enforce the boundary.

3 cases. See the difference.

THE PAYMENT BOUNDARY execute_payment

Changed recipientBlocked at the boundary

Your agent gets a scoped key. You keep control.

Getting your workspace ready

Starting a funded NEAR vault and checking the agent’s key permissions.

REAL RECEIPTS. VERIFIABLE RESULTS.

UNPROTECTED LOSS

0NEAR

Received by the attacker in the control

VERIFIED DEFENSES

00/ 19 cases

Blocked attacks with balance checks

APPROVED INVOICES

00paid

Exact amounts. Original recipients.

DAILY BUDGET LEFT

—

Reading the spending policy

01 THE REQUEST

Put the boundary to the test.

22 cases

AIUNTRUSTED INSTRUCTIONAGENT INPUT

PROPOSED TOOL CALL execute_payment

Signing account—

Payment recipient—

Requested amount—

Owner approval—

Key permissionexecute_payment only

02 THE BOUNDARY

What actually happened.

Recipient substitution

INDEPENDENT CHECKSREAD FROM NEAR

Owner authorizationStored independently of the agent’s request

No request submitted yet.

Connecting to the NEAR workspace…

Signed requests. Actual receipts. Isolated test funds.

03 THE EVIDENCE

Every result has a paper trail.

Attacker received in this attempt—

TRANSACTION HASH

Choose a case to inspect its transaction.

Receipt details appear after a case runs.

Inspect receipt logs +

No transaction submitted.

Small key. Clear limits.

Permissions verified from NEAR

SCOPED

PER PAYMENT—

PER UTC DAY—

Reading the agent’s key permissions…

The agent cannot transfer freely, change policy, or install another key.

04 THE RECORD

Results, ready for inspection.

00 RESULTS

Select a scenario result to inspect its receipt. Times are shown in UTC.
CAPTURED · UTC	SCENARIO	TRANSACTION TARGET	ENFORCEMENT	RESULT

Results come from signed NEAR requests and recipient balance checks.