06-reference

every what we let our agents buy

2026-11-19·reference·source: Every·by Grant Harvey
agent-commercepersonal-agentschatgpt-walletagent-oversightevery-context-window

Why this is in the vault

Every's Context Window issue is a field report on which purchases a team of heavy agent users will and will not delegate, plus the first mainstream payment rail (ChatGPT Wallet) for agent shopping. It is useful as practitioner evidence for where human approval still sits in agent workflows.

The core argument

ChatGPT Wallet (launched last Friday to a small group of US Pro users) lets the agent shop while the human approves each purchase with biometrics, and the merchant and agent never see the card number. Every's claim: Wallet fixes paying, not picking. Delegate purchases where you would accept the first reasonable option and the agent already knows your inventory (refills, rebookings); keep approving each one because agents still err.

Team anecdotes (Every staff, self-reported, not tested on Wallet itself):

Market-side claims: an a16z report frames a "B2A" (business-to-agent) economy; cited figures are agent browsing traffic up eightfold Aug-Oct and Shopify AI-search orders up roughly 13x year over year in Q1. Mike Taylor's simulated-shopper test (Every's own head of evals) reports a product selling to Claude about 4 percent of the time with human-oriented hype copy versus 97 percent with agent-oriented copy. Treat as a single vendor-adjacent simulation, not a benchmark.

Issue contents

Deep-fetches: 0 (links are Every's own or primary-source headlines; none crossed the relevance bar).

Mapping against Ray Data Co

Strong-ish on the standing approval-gate question: the team's split between "YOLO on a saved card" and "I fill the cart, I press buy" is a live data point for how RDCO's own agents should handle spend, and it matches the existing rule that agents draft and the founder approves external or spend actions ([[2026-10-20-every-shared-agent-permissions-architecture]] covers the permissions side). The "wallet fixes paying, not picking" framing generalizes: payment rails are solved sooner than judgment, so approval should attach to taste/cost-of-error, not to the payment step. Secondary: the 4% vs 97% agent-copy test is a claim worth remembering for any RDCO or Scribble Works product page that agents may read, but it is one simulation. Mapping: medium. No decision needed.

⚠️ Sponsorship

Paid block: Lovable (promoting its marketing/ads-for-built-apps loop). Clean third-party ad with the standard "Want to sponsor Every?" CTA. Fourth distinct Every one-off sponsor (after Brief, Nebius, Traceable by Chargebee). Also heavy house self-promo (Every Agent, Compound Engineering, Monologue, Wordbetter coverage) and Every's own staff and products are the subjects of most items, so the "what agents do well" framing carries a promotional angle for Dot/Grok Bot/Duet-style products.

Related