# GPT-4 Turbo API Rate Limits, Pricing & Performance (July 2026)

- Tool: AI API Limits & Performance Matrix
- Last updated: July 2026

## TL;DR

GPT-4 Turbo is not on OpenAI's current pricing table as of July 2026 — it is delisted and superseded by GPT-4.1 (1M context) and the GPT-5 line. Current first-party pricing is not published. Fine-tuning is blocked for new organizations since May 7, 2026; existing org fine-tuning ends January 6, 2027. If you are hitting 429 errors on existing GPT-4 Turbo integrations, the playbook below applies — migration to GPT-5.5 or GPT-4.1 is the recommended long-term fix.

## Frequently asked questions

### Is GPT-4 Turbo still available?

The GPT-4 Turbo API endpoint (gpt-4-turbo) remains callable as of July 2026, but it is delisted from OpenAI's current pricing table. No official shutdown date has been announced for API access. Fine-tuning is blocked for new organizations since May 7, 2026.

### What are the GPT-4 Turbo API rate limits?

OpenAI does not publish per-tier rate limits for GPT-4 Turbo as of July 10, 2026 (delisted model). Historical GPT-4-class Tier 1 was approximately 500 RPM / 10,000–30,000 TPM — but these figures are from pre-2026 third-party trackers and may no longer reflect current allocation. Check your actual limits in the OpenAI dashboard.

### What is the GPT-4 Turbo price per token?

GPT-4 Turbo pricing is not published (delisted) as of July 2026. Historical third-party data (pre-delisting) showed approximately $10.00 input / $30.00 output per MTok — but these are not current first-party figures. OpenAI recommends GPT-5.5 ($5.00/$30.00/MTok) or GPT-4.1 nano ($0.10/$0.40/MTok) as replacements.

### What should I migrate GPT-4 Turbo to?

For most chat/completion use cases, migrate to GPT-5.5 (model: "gpt-5.5") — same API shape, 1M context, and published pricing. For budget-sensitive or high-volume workloads, GPT-4.1 nano (model: "gpt-4.1-nano") at $0.10/$0.40/MTok is OpenAI's recommended low-cost path.

### When does GPT-4 Turbo fine-tuning end?

Self-serve fine-tuning for GPT-4 Turbo was blocked for new organizations as of May 7, 2026. Existing organizations have until January 6, 2027 to complete fine-tuning. No deadline has been announced for the base API endpoint.

### How do I fix a 429 error on GPT-4 Turbo?

Check the Retry-After header on the 429 response and wait that many seconds. Implement exponential backoff with jitter (1s start, double each retry, max 60s). OpenAI uses rolling 60-second windows, so waits are usually short. Long-term: migrate to GPT-5.5 for better capacity allocation.

### GPT-4 Turbo vs GPT-5: which should I use?

GPT-5.5 for all new projects. GPT-4 Turbo is delisted with no published pricing, has a shorter 128K context, older knowledge cutoff (April 2024), and receives lower capacity allocation as a legacy model. GPT-5.5 is cheaper per input token than historical GPT-4 Turbo pricing and offers 1M context.

### Can RapidDev help migrate our GPT-4 Turbo integration?

Yes. RapidDev engineers handle GPT-4 Turbo to GPT-5.5 migrations including API updates, prompt caching setup, and fine-tuning migration planning. Book a free scoping call at rapidevelopers.com/contact.

---

Source: https://www.rapidevelopers.com/ai-api-limits-performance-matrix/gpt-4-turbo
© RapidDev — https://www.rapidevelopers.com/ai-api-limits-performance-matrix/gpt-4-turbo