A shopper can authorize an AI assistant to buy something without settling whether the retailer permits the automation. Superpower Daily’s bounded public-document review finds three different boundaries: eBay requires permission for automated access, Walmart for automated information gathering, and Etsy for scraping and covered API uses. Approved purchasing routes exist, but with defined limits.
Original analysis: permission for which action?
Our question was practical: which browsing, account-access, purchasing and post-purchase actions require retailer permission beyond buyer consent? We compared saved public terms and official integration documents for U.S. consumer workflows at eBay, Walmart and Etsy. The comparison distinguishes permission requirements, prohibitions, supported integration routes and indeterminate cases; missing language is neither permission nor a ban.
The requested cutoff was October 14, 2026, at 15:30 UTC, but the supplied snapshots were retrieved afterward, so their availability at that exact time is unverified. This review covers published rules, not access testing, enforceability or comparison with earlier versions; it does not establish technical blocking or when the restrictions were introduced.
eBay puts permission before automated access
The clearest broad rule appears in eBay’s User Agreement, effective June 28, 2026, for existing users. It requires prior express eBay permission for automated access to its services for any purpose. The language explicitly includes buy-for-me agents, large-language-model bots and end-to-end flows that attempt orders without human review.
That makes the boundary wider than payment: automated browsing, account access and post-purchase access fall within the access rule too. A buyer approving the eventual order does not supply eBay’s required permission. Human review of a purchase is therefore not a substitute for authorization to automate access.
Account access has another condition. eBay separately prohibits sharing login credentials with third parties and points authorized third parties toward its Multi-User Account Access program. Permission to automate and the method used to enter an account are separate questions. Giving an assistant a password is not an alternative authorization route under that language.
There is a documented buying-integration route, but it requires more than opening a developer account. eBay’s Buy API requirements call for eligibility checks, approvals and contracts before production access. An API is a software interface for interacting directly with a service. Member checkout requires approval, as do guest and member checkout methods in the sandbox—the testing environment.
We advise you to complete the Production application process and obtain approval before you invest significantly in application development and testing.
eBay, Buy APIs Requirements
Walmart’s information rule leaves other actions unresolved
Walmart’s examined language is specific about gathering site materials. Section 2 of its Terms of Use requires express prior written consent for automated retrieval, indexing, scraping, data mining or other gathering. The restriction reaches product-information collection, not just checkout. It separately prohibits systematically downloading and storing materials.
Unlike eBay’s broad access rule, these sections do not expressly impose a distinct approval requirement on every delegated login, checkout or return. Those actions remain indeterminate, although gathering information within them can trigger the written-consent requirement. Walmart incorporates additional service terms, and the supplied snapshot is truncated beyond the examined sections.
Walmart’s own shopping integrations provide an important counterpoint to a blanket-ban interpretation. In a company-published conference transcript from March 4, 2026, executive Daniel Danker described ChatGPT purchasing and a planned transition to embedding Walmart’s Sparky assistant inside ChatGPT and Gemini, including account-aware carts. That transition was a plan; its completion by October is unverified.
Etsy separates scraping, developer access and guest orders
Etsy illustrates why contractual scope matters. Its ordinary Terms of Use require express permission to crawl, scrape or spider service pages. They discuss responsibility for shared accounts, but do not expressly authorize AI delegation. Non-scraping browser login, checkout and returns remain unresolved under those ordinary terms alone.
The API Terms impose another layer: developers must submit an application’s purpose for prior approval, and automated systems accessing Etsy sites, APIs or data require written authorization. Collecting member ID-and-password combinations and circumventing checkout are separately prohibited. That broader automation clause belongs to the API agreement; it cannot be applied unconditionally to every non-API browser agent.
Etsy’s buyer help page documents an affirmative route: U.S. shoppers can purchase selected listings through partnered ChatGPT, Gemini, Google AI Mode and Copilot experiences. Shoppers sign into the partner service, then check out as Etsy guests. The purchase is not automatically connected to an existing Etsy account.
The route has practical limits beyond listing eligibility. Transactions are in U.S. dollars, and Etsy gift cards and coupons cannot be used. A supported AI checkout experience therefore does not necessarily reproduce every payment or discount option a shopper expects.
Reader comments
Newest comments first. Replies stay oldest first.