Not going to work for very long or at any scale coming from datacenter/hosting provider IPs. Google "residential proxies for sale" for the tip of an iceberg of how they snowshoe the traffic.
I use my Codex and Claude Code subs on like 4-6 different servers, ranging from AWS to Vultr to Linode etc.
That’s a major and legitimate use case for developers, Anthropic can’t just block data center/hosting IPs because their actual customers use them on data center/hosting IPs.
Now consider what will happen if your pattern of queries and context history triggers a pattern that makes it obvious it's some API key being used by multiple different entirely unrelated people on totally different things, or any other pattern of use that makes it obvious it's being used for distillation.
Respectfully, no, that's not how it works. You think the people running anti-fraud and anti-bot measures don't have tools that know the specific ipv4 and ipv6 CIDR ranges of every ASN that they categorize as hosting/colo providers?
And that's just as a basic first effort reject measure to prevent automation tools from using things designed for human-interactive use only.
Go try to do many of these things from Cogent IP space and see how long your project lasts.
Not going to work for very long or at any scale coming from datacenter/hosting provider IPs. Google "residential proxies for sale" for the tip of an iceberg of how they snowshoe the traffic.
I use my Codex and Claude Code subs on like 4-6 different servers, ranging from AWS to Vultr to Linode etc.
That’s a major and legitimate use case for developers, Anthropic can’t just block data center/hosting IPs because their actual customers use them on data center/hosting IPs.
Now consider what will happen if your pattern of queries and context history triggers a pattern that makes it obvious it's some API key being used by multiple different entirely unrelated people on totally different things, or any other pattern of use that makes it obvious it's being used for distillation.
1 reply →
As long as you stick to a single unique IP per account it isn't going to get flagged.
Respectfully, no, that's not how it works. You think the people running anti-fraud and anti-bot measures don't have tools that know the specific ipv4 and ipv6 CIDR ranges of every ASN that they categorize as hosting/colo providers?
And that's just as a basic first effort reject measure to prevent automation tools from using things designed for human-interactive use only.
Go try to do many of these things from Cogent IP space and see how long your project lasts.
9 replies →
Hey, if the bastards can use residential IPs to suck all information into their models with their crawlers, so can we!
There are lots of botnets providing home IPs.