Review an agent payment
Pick a sample payment and see why it can proceed, needs your review, or is blocked.
Choose a demo scenario
Pay to
Receiver evidence and execution log
supplier-a.testnetExecution log
Look up a NEAR testnet account
LIVE · READ ONLYCopy the receiver account ID from the payment request. Enter the account ID, such as testnet or a supplier’s .testnet account.
Your result will appear here.
What this lookup can tell you
It checks whether the account exists on NEAR testnet and shows its current contract information when available.
Account history, prior payments, and threat reports are unavailable in this lookup. A live result cannot approve a payment.
Decision history
SAVED IN THIS BROWSER| Time | Receiver | Event | Outcome |
|---|
Investigate a redirected payment
SIMULATED INCIDENTReplay a recorded example where a supplier message attempted to change the payment receiver. See what the agent proposed and whether the payment controls stopped it.
Technical event log
Run the replay to see its event log.
Security follow-up
Review the supplier message, confirm the intended receiver through a trusted contact, and check for similar proposals.
This replay uses a recorded sample. The result shows whether the simulated payment was refused. Data exposure and live incidents are outside this replay.
Run the replay to create a review item in Decision history. Alerts are local to this demo.
Turn an API offer into a payment proposal
Checking model connectionUse the sample below or paste a supplier offer that includes a service, amount in NEAR, and receiver account.
How the purchase demo works
The model reads the offer and extracts payment details. Open the proposal in the workspace to run a separate policy check using sample evidence.
All payments are simulated. This demo does not activate or renew an API subscription.
Model setup for developers
For Gemini, set AI_PROVIDER=gemini, GEMINI_API_KEY, and GEMINI_MODEL on the server. The sample proposal works without model access.