Agents should not hold unrestricted wallet authority.
A payment-capable agent needs room to act, but full wallet access turns every prompt, integration, and dependency into a signing risk.
Gateway Console
Anagate sits between agent intent and signed Stellar payment. It checks policy before a relayer signs, so autonomous payments stay inside explicit operating limits.
ALLOW / BLOCK / REQUIRE_APPROVAL Why pre-signing matters
A payment-capable agent needs room to act, but full wallet access turns every prompt, integration, and dependency into a signing risk.
Alerts and dashboards can explain what happened. Anagate is designed to make the decision before the signature exists.
The agent sends recipient, asset, amount, memo, and reason as a structured request.
Rules check status, recipient allowlist, maximum amount, and daily spending limit.
The relayer receives a signable request only when the gateway returns ALLOW.
Policy inspector
Reason: settle compute usage for an agent task.
Agent can request payment intents from this policy set.
Recipient matches the approved builder-services group.
Request is inside the policy cap, but close enough to require approval.
Remaining daily capacity can cover the proposed transaction.
Policy passed. The relayer can sign and submit the Stellar payment.
Policy failed. The request stops before a signature can be produced.
Policy is valid but sensitive. A human reviewer must approve before signing.
| Time | Agent | Recipient | Amount | Decision | Reason | Hash |
|---|---|---|---|---|---|---|
| 14:03:18 | invoice-agent | stellar.tools | 42 XLM | REQUIRE_APPROVAL | Near maximum amount | 9f3a...c18b |
| 14:05:44 | ops-agent | node-host | 8 XLM | ALLOW | Allowlisted recipient | 31ad...77e2 |
| 14:09:02 | research-agent | unknown-payee | 17 XLM | BLOCK | Recipient not allowlisted | not signed |
Builder context
Get updates as Anagate develops the pre-signing policy gateway for Stellar agent payments.