Stealing AI calls has become big business: how Vercel is fighting it
Hackers steal paid AI calls, wrap them in an OpenAI-compatible API and resell them through proxies. Ordinary rate limits don't help. Vercel faced an attack of 1,300 requests per minute, which would have cost $10k a day without protection. The company has explained how the scheme works and how it stopped it. The core problem is economics: the attacker pays nothing, resells tokens at a discount and keeps the profit.
AI-processed from Vercel Blog; edited by Hamidun News
Hackers have found a new way to monetize other people's AI calls. They steal your paid requests to Claude, GPT or Gemini, wrap them in a compatible API and resell them through proxy networks, with zero spending on the inference itself.
The economics of theft
A single prompt call to a frontier model can cost $2, while an HTTP request on Vercel costs $2 per million. AI inference is a million times more expensive, which makes it one of the most lucrative things to steal. The attacker pays nothing, then resells tokens at a 10–20% discount to the original price, still a huge profit on zero costs.
A typical scenario: the attacker builds an OpenAI-compatible adapter that wraps your AI endpoint. They then fan out requests across hundreds of residential proxy IPs and either release the ready-made SDK publicly or sell a subscription.
- Examples exist: Chipotlai Max wraps the Chipotle chatbot
- It openly asks for help porting to Home Depot, Lowe's and Target
- The adapter is a session boundary for the attacker's downstream users
Why rate limits don't save you
Defenses such as rate limits and auth walls were designed for attacks with radically different economics, where the cost of bypassing them exceeded the profit. Here the profit is enormous: attackers buy residential proxies by the thousand and create as many fake accounts as they need. Rate limits get diluted across hundreds of IPs.
The classic bug: you check the user once per session, then send every request on to the AI. The attacker hijacks the session and pushes thousands of stolen calls through it. By the time a request reaches your API, it has already crossed your line of defense. Verification has to run on every call, not on the session.
The real attack on Vercel
On April 29, 2026, traffic to the AI chat in Vercel's documentation jumped 10x, to 1,300 requests per minute on the Claude Haiku 4.5 model. At current prices that would have cost $10k+ a day. The company spotted the mass theft through pattern monitoring and stopped the attack with deep per-request BotID analysis.
"If you have an AI endpoint on the internet, the risk of abuse is huge and can easily lead to bills in the tens of thousands of dollars," says
Vercel.
What this means
Inference theft is now a real threat for any company that has put an AI endpoint on the internet. Rate limits and basic auth are not enough. You need deep analysis of every request, not of the session. For startups and SaaS companies, moving to per-request verification is something to do now, not later.
- Nov 1, 2026Kimi scores 96.2% on a 1C database analytics test and emerges as a fallback if Claude access is blocked
- Nov 1, 2026OpenAI Rewrites GPT Behavior Rules: Five Values and a Chain of Command
- Nov 1, 2026Google admits AI Mode cuts search revenue, shares fall 15%
- Oct 31, 2026Author puts his script before an AI jury: the verdict cost 850 thousand tokens
Key Questions Answered
What are the key details on The economics of theft?
A single prompt call to a frontier model can cost $2, while an HTTP request on Vercel costs $2 per million. AI inference is a million times more expensive, which makes it one of the most lucrative things to steal. The attacker pays nothing, then resells tokens at a 10–20% discount to the original price, still a huge profit on zero costs. A typical scenario: the attacker builds an OpenAI-compatible adapter that wraps your AI endpoint. They then fan out requests across hundreds of residential proxy IPs and either release the ready-made SDK publicly or sell a subscription. Exa
Why rate limits don't save you?
Defenses such as rate limits and auth walls were designed for attacks with radically different economics, where the cost of bypassing them exceeded the profit. Here the profit is enormous: attackers buy residential proxies by the thousand and create as many fake accounts as they need. Rate limits get diluted across hundreds of IPs. The classic bug: you check the user once per session, then send every request on to the AI. The attacker hijacks the session and pushes thousands of stolen calls through it. By the time a request reaches your API, it has already crossed your line
What are the key details on The real attack on Vercel?
On April 29, 2026, traffic to the AI chat in Vercel's documentation jumped 10x, to 1,300 requests per minute on the Claude Haiku 4.5 model. At current prices that would have cost $10k+ a day. The company spotted the mass theft through pattern monitoring and stopped the attack with deep per-request BotID analysis. "If you have an AI endpoint on the internet, the risk of abuse is huge and can easily lead to bills in the tens of thousands of dollars," says Vercel.
Ship AI Faster with Founders, Engineers & Weekly Architecture Reviews
Inside Vibe Club (hamidun.com/club) — weekly live masterminds with Zhemal Khamidun, Tech Radar, full LMS access, and 370+ production Claude Code skills.
The AI world, distilled — once a week
Seven stories that actually mattered, hand-picked. No noise, no reposts, no press releases.
Done! Check your inbox for a confirmation.