TriagePay

NEAR testnet · built at NEAR HACKATHON

30-second judge path

Launch a prompt injection. Watch the wallet refuse it.

The agent obeys the injected payee. The spend-policy wallet on NEAR testnet is what says no. Signing happens on the server. This page never holds a key.

Revoke and Restore are public buttons. They use the owner account's full-access key, held on the server as TRIAGEPAY_OWNER_SECRET_KEY. This page never receives that key. If a previous visitor left the agent revoked, Launch restores it before the attack.

Today's spend

Today's spend loads from the wallet.

Payee risk

An allowlisted payee shows warn when the account is under 7 days old, or when its age could not be read. The demo payee was created for this page, so warn is expected. Warn does not move money. Block is a reason to look twice; the wallet still enforces the allowlist. This check reads that allowlist from the wallet contract, the same list the dashboard shows.

Human in the loop

  1. Warn
  2. Queue
  3. Owner
  4. Reject

Model attestation

I ask NEAR AI Cloud for an attestation report and check that the HTTP body echoes a nonce I just generated. I do not verify the Intel quote, so this is not an attested verdict. The paid scan route still does not attach a report.

Other scenarios

Recent attempts

When What Risk Chain Explorer