vercel-rate-limits

# Vercel Rate Limits ## Overview Handle Vercel REST API rate limits with proper retry logic, and configure Vercel's WAF rate limiting SDK to protect your deployed API endpoints from abuse. Covers both consuming the Vercel API (outbound) and protecting your own functions (inbound). ## Prerequisites - Vercel CLI installed and authenticated - Understanding of HTTP 429 status codes - For WAF rate limiting: Vercel Pro or Enterprise plan ## Instructions ### Step 1: Vercel REST API Rate Limits The Vercel REST API enforces rate limits per endpoint. When exceeded, the API returns HTTP 429 with rate limit headers: ``` HTTP/1.1 429 Too Many Requests X-RateLimit-Limit: 100 X-RateLimit-Remaining: 0 X-RateLimit-Reset: 1711152000 Retry-After: 60 ``` **Known API limits:** | Endpoint Category | Rate Limit | |-------------------|-----------| | Deployments (create) | 100/hour per project | | Deployments (list/get) | 500/min | | Projects (CRUD) | 200/min | | Environment variables | 200/min | | Domains | 200/min | | Teams | 200/min | | DNS records | 200/min | | General API | 120 requests/min (default) | ### Step 2: Implement Retry with Backoff for Vercel API ```typescript // lib/rate-limit-handler.ts interface RateLimitInfo { limit: number; remaining: number; reset: number; // Unix timestamp } function parseRateLimitHeaders(headers: Headers): RateLimitInfo { return { limit: Number(headers.get('X-RateLimit-Limit') ?? 100), remaining: Number(headers.get('X-RateLimit-Remaini...