Amazon shows Grok Bots an unauthorized-agent page; Musk says shop elsewhere

If your Bot shops or handles returns on Amazon, expect it to hit a wall. Users report that Amazon now shows their Bots a page reading "Continued access by an unauthorized AI agent violates Amazon's Conditions of Use, to which our customers have agreed." Don't try to sneak past it. Point the Bot at other stores, and do Amazon orders and returns yourself for now.

• Who: Grok Bot users who send Bots to amazon.com. Nobody has published a count.
• Symptom: the Amazon page above, with a single Continue button, in place of the store.
• Risk: Amazon's terms ban agents from getting around its blocks, so workarounds put your Amazon account in play, not just the order.
• Status: no statement from Amazon or the Grok Bot team. Elon Musk's answer is to buy elsewhere; his SpaceX make-whole line is his own pledge, not Cursor policy.

What changed#

Reports started on the afternoon of Oct 14. At 2:25 PM ET, Farzad shared a screenshot of it and wrote "I am not an agent." At 11:21 PM ET, Nic Cruz Patane posted the same page and said "My bots can no longer access Amazon for orders or anything." By this morning the reports were trending on X, and one new user said their first Bot, a Comixology wish list checker, "failed" on day one "because @amazon blocked it."

Musk's answer was to go around Amazon, not through it. He replied at 9:22 PM ET Oct 14: "Just ask Grok Bot to find the best deal on the Internet for what you want. Doesn't need to come from Amazon." He added that his "Bot bought LEGO directly from the LEGO website no problem," and at 1:24 AM ET he told users: "Just ask Grok @Bot to buy what you want someplace else and get a better deal. There are far more purchasing websites than just Amazon!"

At 1:57 AM ET, quoting a user whose Bot booked a flight, Musk added: "If Grok @Bot makes a mistake with a purchase or leaks your card (never happened yet), SpaceX will make you whole." At 8:52 AM ET he mused "Maybe we should start a competitor to Amazon," a post with more than 2.6 million views by noon.

Why it matters#

The block is written into Amazon's rules. Its Conditions of Use, last updated Aug 14, 2026, now have an Agents section covering "any software or service that takes autonomous or semi-autonomous action on behalf of, or at the instruction of, any person or entity." Agents must name themselves in every request by putting "Agent/[agent name]" in the user agent string, must not conceal themselves by "mimicking the speed or pattern of human keystrokes" or by "completing or circumventing CAPTCHAs," and must "Not circumvent or otherwise avoid any measure intended to block, limit, modify, or control whether and how Agents access" Amazon Services. Amazon also says that "At our sole discretion, we may limit, including by technical measures, whether and how any Agent accesses" its services.

That rules out the usual fix. Cursor's help center says that when a site blocks cloud computers you can turn on Route traffic through this computer so "sites see your own connection." Our note: on Amazon, using that to get past an agent block is the kind of workaround its Agent Terms forbid (Amazon does not name Route traffic; this is our reading of the "Not circumvent" rule). One user also reports that "amazon detects Grok Bots VM even when egress routing is on." We haven't verified that.

Musk's pledge matters too, but it's a post, not a policy. We found no written version on Cursor's help, FAQ or security pages as of 12:30 PM ET, and the post doesn't say how to file a claim.

What to do now#

1. Move Bot shopping off Amazon. Try:

Find the best price for [item] at stores other than Amazon. Show me the top 3 with the total price including shipping, the delivery date and the return policy. Don't buy anything yet. When I pick one, add it to the cart and hand me the checkout so I can pay.

2. Do Amazon orders and returns yourself. If a Bot handled your Amazon returns, take that job back for now.
3. Let a Bot track Amazon from your email instead of the site. Reading order and shipping emails through a connected email plugin doesn't touch amazon.com. For example: "Each morning, check my email for Amazon order, shipping and return emails and give me a list of what's arriving and which return windows close this week."
4. Don't turn on traffic routing just to get back into Amazon, and don't ask your Bot to complete or circumvent Amazon's CAPTCHAs or other checks. Our note: both look like the Agent Terms' no-conceal and no-circumvent rules above.

Good to know#

• Don't send a photo of your card. The flight booking Musk praised started with the user saying "I send a photo of my credit card." Cursor's security docs say that "For login, two-factor, and payment steps, the Bot hands the computer to the member rather than typing credentials," and that "passwords and one-time codes never belong in ordinary chat." When a Bot asks for a secret, use the secure secret card, which keeps the value out of the chat.
• The page can appear for people too. Farzad posted it with "I am not an agent," so the check may catch some human sessions.
• Musk's "never happened yet" is his claim. The pledge names purchase mistakes and leaked cards, and nothing else.
• "Maybe we should start a competitor to Amazon" ended in a thinking emoji. It isn't an announced product.

What to watch#

Any written terms for Musk's purchase pledge, any word from Amazon on whether named agents can apply for access, and saved web logins for Bots. When a user asked Musk on Oct 14 to "Allow it to save web passwords - it keeps making me log in!", he replied "Coming very soon" at 11:02 PM ET. Treat that as a hint, not a date.