Back to blog
Workflow
Vercel

Why does bursty AI traffic still leave you stuck in retry queues?

Thắng Đoàn
Thắng Đoàn

When bursty AI workloads hit provider rate limits, time-sensitive batch jobs can stall in retry queues and burn most of a client's deadline. Mercor fixed this by routing model traffic through Vercel AI Gateway for extra capacity and automatic failover between providers.

What it is

Vercel AI Gateway manages model access across providers and fails requests over to another provider when rate limits hit. Paired with Vercel Passport, it also provisions secure access to internal applications in seconds.

Applied case

Mercor runs large automated grading batches for AI labs, with demand bursts that push model traffic to peak capacity for days. Its old mix of direct integrations and third-party gateways lacked token-per-minute capacity, so batch jobs stretched beyond 12 hours of a 24-hour deadline. With failover routing through AI Gateway, those jobs dropped to 2 hours. Over 10 days, Mercor routed 18M requests and 63B tokens through the gateway, while Passport provisioned expert access in seconds across more than 2,000 internal projects.

  • Gateway failover kept batch jobs running instead of idling in retry queues

When to use it

Use when bursty AI workloads hit provider rate limits and client deadlines are at risk. Skip when one provider already gives you enough capacity and routing control.

  • Does not solve provider-side capacity ceilings when no provider has headroom
  • Does not remove deadline risk if your jobs themselves exceed the remaining window

Read more

Mercor on Vercel

Vercel AI Gateway

Vercel Passport

Share:

Recommended for you

Enjoyed this article?

Subscribe for new articles. No spam. Unsubscribe anytime.

By subscribing you agree to receive the newsletter. No spam, and you can unsubscribe anytime.