MetaMask is the permission surface
The workbench connects through the injected wallet when available, requests eth_requestAccounts, then asks for eth_signTypedData_v4 on the scoped spend package.
Project boundary
It is a public judging surface for one concrete question: should this agent be allowed to buy this x402 resource under this wallet policy?
The workbench connects through the injected wallet when available, requests eth_requestAccounts, then asks for eth_signTypedData_v4 on the scoped spend package.
Each approved or blocked case shows the kit version, implementation, DelegationManager, EIP-7702 path, caveats, enforcers, and hashDelegation output.
Approved requests prepare a relayer-ready x402 packet with seller, resource, cadence, category, and max payment units. Live relay credentials are stated as a boundary.
The policy route enriches the request through a Venice-compatible note when configured, or clearly labels local fallback mode in the UI and saved case.