Let Grok Shop? Decide What It Can Spend First.

Elon Musk last week encouraged followers to send Grok Bot a photograph of their credit card so the agent could search online and order products, Futurism reports. The next day, Musk posted a screenshot of an instruction to research LEGO Star Wars kits for young children and buy them. The screenshot exposed his order number, email address, and the last four digits of his card.

A user named Enderman then claimed to have persuaded LEGO’s customer service bot to cancel the order. Musk denied that the cancellation happened. Other users posted further claims of order manipulation, but the supplied reporting does not verify those outcomes. The established mistake was publishing transaction information. The alleged pranks do not establish that Grok itself mishandled the purchase.

Comparison shopping is a reasonable job to outsource. An assistant that checks prices and prepares a cart could help someone who already knows what to buy. Musk’s pitch goes further: the software chooses an offer and places the order. The shopping assistant should not promote itself to account holder. A successful demonstration of checkout does not establish the boundaries of that authority.

Set the limit before supplying the card

Before enabling purchases, verify whether the service supports a hard spending cap, a defined product request, and confirmation of the final total. A prompt saying “keep it cheap” is not evidence of an enforced limit. If the agent chooses the merchant, the customer also needs a way to inspect that choice before payment. Musk’s promise to find the best deal is promotional language, not an independently tested comparison.

Next, establish who handles a wrong item, an unwanted order, or a purchase from a deceptive store. Futurism reports that scammers target shopping agents with fake storefronts and manipulated recommendations. That risk does not prove this order involved fraud. It does mean that finding a low price and identifying a trustworthy seller are separate tasks. Do not assume that card protections resolve every dispute involving a purchase the customer delegated; check the issuer’s terms and the service’s account of responsibility.

Revocation needs equal attention. Customers should verify how to stop future purchases, remove stored payment information, and identify orders already submitted. Those are different operations. Removing a card from a chat would not, by itself, demonstrate that every stored copy or active permission had disappeared. The supplied account does not establish Grok’s controls for those steps, its retention terms, or its allocation of losses.

If documented controls let you approve each total, restrict spending, and withdraw permission, delegated shopping may be useful for a narrow, routine purchase. If those controls remain unclear, use the assistant for research and complete checkout yourself. A photograph of a credit card is easy to send. The terms governing what happens afterward deserve more effort.