<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: When Can Amazon Block an Agentic AI Service?&#8211;Amazon v. Perplexity (Guest Blog Post)	</title>
	<atom:link href="https://blog.ericgoldman.org/archives/2026/06/when-can-amazon-block-an-agentic-ai-service-amazon-v-perplexity-guest-blog-post.htm/feed" rel="self" type="application/rss+xml" />
	<link>https://blog.ericgoldman.org/archives/2026/06/when-can-amazon-block-an-agentic-ai-service-amazon-v-perplexity-guest-blog-post.htm</link>
	<description></description>
	<lastBuildDate>Sat, 06 Jun 2026 20:29:00 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Charles Barton		</title>
		<link>https://blog.ericgoldman.org/archives/2026/06/when-can-amazon-block-an-agentic-ai-service-amazon-v-perplexity-guest-blog-post.htm#comment-4633</link>

		<dc:creator><![CDATA[Charles Barton]]></dc:creator>
		<pubDate>Sat, 06 Jun 2026 20:29:00 +0000</pubDate>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=28938#comment-4633</guid>

					<description><![CDATA[I think there is an important factual distinction that the post does not address sufficiently: whose computer is actually performing the interaction with Amazon?

If Perplexity&#x27;s software runs on the user&#x27;s own machine and merely automates the user&#x27;s browsing, the delegated-agent theory becomes considerably stronger. In that scenario, the software looks more like (or is) a browser, screen reader, password manager, or other user-selected tool operating on the user&#x27;s behalf.

If, however, Perplexity runs cloud-based agents from Perplexity-controlled infrastructure that independently connect to Amazon, then courts are more likely to view Perplexity itself as the actor accessing Amazon&#x27;s computers. That characterization fits more comfortably within the existing CFAA and Power Ventures framework.

The post argues that the key issue is whether users may delegate ordinary account activity to software. But before reaching that question, it seems necessary to ask where the software is running and who is transmitting the requests to Amazon. The answer may determine whether the interaction is best understood as the user&#x27;s own browsing through an automated tool or as Perplexity&#x27;s access to Amazon&#x27;s systems.

That omission strikes me as one of the strongest weaknesses in the analysis. The legal consequences may differ substantially depending on the technical architecture.]]></description>
			<content:encoded><![CDATA[<p>I think there is an important factual distinction that the post does not address sufficiently: whose computer is actually performing the interaction with Amazon?</p>
<p>If Perplexity&#x27;s software runs on the user&#x27;s own machine and merely automates the user&#x27;s browsing, the delegated-agent theory becomes considerably stronger. In that scenario, the software looks more like (or is) a browser, screen reader, password manager, or other user-selected tool operating on the user&#x27;s behalf.</p>
<p>If, however, Perplexity runs cloud-based agents from Perplexity-controlled infrastructure that independently connect to Amazon, then courts are more likely to view Perplexity itself as the actor accessing Amazon&#x27;s computers. That characterization fits more comfortably within the existing CFAA and Power Ventures framework.</p>
<p>The post argues that the key issue is whether users may delegate ordinary account activity to software. But before reaching that question, it seems necessary to ask where the software is running and who is transmitting the requests to Amazon. The answer may determine whether the interaction is best understood as the user&#x27;s own browsing through an automated tool or as Perplexity&#x27;s access to Amazon&#x27;s systems.</p>
<p>That omission strikes me as one of the strongest weaknesses in the analysis. The legal consequences may differ substantially depending on the technical architecture.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
