Agent Escrow — x402 Budget Shield

Agent Escrow is a local Chrome side-panel utility for reviewing compatible HTTP 402 and x402 payment-requirement metadata. Create local spending guardrails for automated AI-agent and API payment requests, including: • Automatic-approval ceiling • Hard-stop amount • Daily USDC budget • Trusted domains • Recurring-charge detection • Human review for untrusted or higher-cost requests • Pending review decisions • Local audit history • Chrome notifications for blocked or review-required requests Agent Escrow includes a built-in safe testing sandbox. Reviewers and users can demonstrate APPROVE, REQUIRE_HUMAN, and BLOCK outcomes without sending a payment or connecting a wallet. Optional browser observation can be enabled by the user. When enabled, Agent Escrow inspects compatible HTTP 402 response headers and compares the available payment metadata against the user’s locally saved policy. All policies, pending decisions, approved totals, and audit records are stored locally through Chrome storage. Agent Escrow does not: • Hold or transfer funds • Connect to wallets • Create payment signatures • Submit or settle transactions • Store card information • Receive Stripe payment information • Act as a licensed escrow provider Browser-observation decisions are advisory local records. Compatible agents and payment clients must independently honor the user’s policy decision before completing a payment. PAID ACCESS Installation does not include active access. Available access options: • $29 recurring monthly through Stripe-hosted checkout • $149 one-time payment for 12 months of access Stripe processes payments separately. Agent Escrow does not receive card details, Checkout Session information, subscription status, cancellation status, or renewal status. After checkout, users confirm access locally on their device. The extension does not perform remote subscription, renewal, cancellation, or entitlement checks. PRIVACY Agent Escrow contains no advertising, analytics, tracking scripts, telemetry, or remote executable code. Compatible payment metadata, source URLs, policy settings, pending decisions, and audit history remain locally on the user’s device.