# GPT 5.6 Sol, Luna, and Terra now available on AI Gateway

Source: [Vercel](https://vercel.com/changelog/gpt-5-6-now-available-on-ai-gateway)  
Feed7 permalink: https://feed7.dev/p/gpt-5-6-now-available-on-ai-gateway-106pgsr  
Published: 2026-07-09T00:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

Vercel’s limited preview exposes GPT 5.6 as Sol, Terra, and Luna, giving coding-agent teams flagship, balanced, and lower-cost routing targets behind one gateway.

## Source Summary

Vercel added **GPT 5.6** in a **limited preview** with three variants. Sol is the flagship, Terra targets previous-generation performance at **half the cost**, and Luna is described as the fastest, lowest-cost option in the series.

## Practical Implication

Builders should treat the lineup as a routing decision: reserve Sol for demanding agent work, test Terra as the everyday default, and assess Luna for latency- or cost-sensitive steps. Gateway rules can switch existing traffic without code changes.

## Agent-Ready Context

Vercel added **GPT 5.6** in a **limited preview** with three variants. Sol is the flagship, Terra targets previous-generation performance at **half the cost**, and Luna is described as the fastest, lowest-cost option in the series.

Builders should treat the lineup as a routing decision: reserve Sol for demanding agent work, test Terra as the everyday default, and assess Luna for latency- or cost-sensitive steps. Gateway rules can switch existing traffic without code changes.

The announcement supplies no absolute prices, benchmark scores, latency figures, or preview access details. Claims of stronger agentic performance and improved token efficiency need workload-specific evaluation before changing production defaults.

## Context Map

- Layer: model
- Domains: coding, security
- Topics: model-selection, reasoning, coding-agents

## Uncertainty

- The announcement supplies no absolute prices, benchmark scores, latency figures, or preview access details. Claims of stronger agentic performance and improved token efficiency need workload-specific evaluation before changing production defaults.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.