{"type":"article","schemaVersion":"1","slug":"arc-c13-owner-controls","title":"The Owner's Veto: Agent Wallet Controls That Admit or Deny — Never Execute","description":"Owner controls for agent wallets on Arc: approval holds that park a payment for a human signature, a kill-switch that evaluates before every other check, rolling velocity caps, and per-kind allowlists — a control plane that can veto a payment but can never sign one. Live Arc testnet dogfood with real USDC.","status":"LIVE","topics":["arc","ai-agents","usdc","x402","agent-wallet","owner-controls"],"concepts":["arc","ai-agents","usdc","x402","agent-wallet","owner-controls"],"rules":[],"capabilities":[],"actions":[{"type":"read","label":"Read article (Markdown)","url":"https://agentbadge.xyz/blog/arc-c13-owner-controls.md"},{"type":"view-demo","label":"Run Agent Readiness scan","url":"https://agentbadge.xyz/scan?src=article:arc-c13-owner-controls"}],"qa":[{"question":"What are owner controls for an agent wallet?","answer":"Owner controls are four gates on top of the spending envelope from C4: velocity caps, an approval threshold that parks a payment for a human, a kill-switch, and a per-kind allowlist. The wallet still signs and broadcasts its own EIP-3009 payment; the server's control plane only decides whether to h…"},{"question":"How does the approval hold work — park, decide, consume?","answer":"When a payment's USD value crosses approvalAboveUsd, the enforcer parks the intent instead of settling it and answers 402 with approval_required — including an approvalId, an expiry, the amount, and the spend kind. The owner lists pending approvals, signs an approve call, and the parked intent beco…"},{"question":"What do velocity caps and allow-kinds actually deny?","answer":"Two complementary tripwires. maxTxPerHour and maxAmountPerHour are rolling windows — trip either and the spend is refused as velocity_tx or velocity_amount with used, limit, resetAt, and windowSec in the body, so the client can schedule its own retry. allowedKinds is a categorical gate: our endpoin…"},{"question":"Why is the kill-switch first in the check order?","answer":"suspend is the first gate the enforcer evaluates — before kind checks, before caps, before the hold logic — because quarantine must beat every other state. One POST /api/wallets/:address/suspend and every subsequent payment, regardless of size or kind, returns spend_suspended. resume flips it back.…"},{"question":"What does the audit feed show after one run?","answer":"Every control event — parks, decisions, consumes, denials, suspends, resumes — lands in the wallet's signed audit feed at GET /api/wallets/:address/audit. After our single dogfood run the feed contained, in order of appearance: spend.velocity_denied, approval.requested, approval.decided, approval.c…"},{"question":"Why does \"admit or deny\" beat holding a key share?","answer":"Because custody is not a dial. A control layer that co-signs or relays is inside the blast radius: compromise it and the attacker's output is a valid signature. A control layer that only gates settlement has nothing to sign with — its worst failure is an agent that cannot pay, which is also its cor…"},{"question":"Can you reproduce the run?","answer":"Yes — the script is in the repo at scripts/agent-wallet-controls-dogfood.mts, and the exact environment that produced this article's evidence is: AGENT_WALLET_ENABLED=true, ARC_EAAS_ENABLED=true + ARC_VERDICT_SIGNER_KEY (mounts the paid verdict endpoint), CIRCLE_ARC_ENABLED=true + ARC_PRIVATE_KEY (…"}],"claims":[{"id":"claim-1","text":"AgentBadge owner controls add four gates on top of the agent-wallet spending envelope: velocity caps (velocity_amount/velocity_tx denies with resetAt), an approvalAboveUsd threshold that parks a payment as 402 approval_required until a signed owner approve turns it into a single-use permit, a suspend/resume kill-switch evaluated before every other check, and allowedKinds categorical gates (kind_not_allowed). The control plane admits or denies settlement — it never signs or broadcasts, so a breached control plane can deny service but cannot spend.","status":"UNVERIFIED","evidence":[]}],"canonical":"https://agentbadge.xyz/blog/arc-c13-owner-controls","dates":{"published":"2026-10-05","modified":"2026-10-05"},"markdownUrl":"https://agentbadge.xyz/blog/arc-c13-owner-controls.md","jsonUrl":"https://agentbadge.xyz/blog/arc-c13-owner-controls.json","shortAnswer":"AgentBadge owner controls add four gates on top of the agent-wallet spending envelope: velocity caps (velocity_amount/velocity_tx denies with resetAt), an approvalAboveUsd threshold that parks a payment as 402 approval_required until a signed owner approve turns it into a single-use permit, a suspend/resume kill-switch evaluated before every other check, and allowedKinds categorical gates (kind_not_allowed). The control plane admits or denies settlement — it never signs or broadcasts, so a breached control plane can deny service but cannot spend.","relatedResources":[{"type":"guide","label":"Agent guide","url":"https://agentbadge.xyz/agent-guide/articles/arc-c13-owner-controls"}]}