Payments & caps
What the agent can spend right now, what's waiting to change, and the evidence of what it did.
reading token metadata...
Reading guard state from chain...
ACTIVEenforced by the contract on every payment, right now
Max per payment
...
Daily limit
...
Spent today (UTC day ...)
...
... · resets 00:00 UTC
PENDINGproposed, not enforced until activated
...
Change the rules
Owner only. Tighter on every axis applies instantly. Anything looser: the tighter part applies now, the rest waits 24h and can be vetoed.
empty list: the agent could pay nobody
token metadata not verified
Turn off this token
Owner only. Instantly removes the active policy and drops any pending change, so the agent can't pay in this token at all.
Agent payment activity
From the agent payment runner's evidence feed. Each status is what the runner reports; every row is re-read from chain and only shows "verified" when the agent's pay call for exactly this request matches.
Reading payment evidence from chain...
"Reserved" means the guard approved the payment, counted it against today's limit and issued the transfer, but the transfer's completion isn't confirmed. "Settled" means the token transfer itself also succeeded. A reservation is never released if the transfer later fails. A row is verified as settled only when the agent's pay call matches this request and the token's own ft_transfer receipt succeeded; a successful guard call with no matching ft_transfer receipt stays "pending".