Skip to main content
Skip to main content

GPT 5.6 Luna

GPT-5.6 Luna is the "moon" of OpenAI's GPT-5.6 family - the lightweight tier built for speed and low cost rather than maximum reasoning depth. Where Sol tackles security research and Terra handles daily professional work, Luna is the model you deploy at scale: classification, extraction, drafts, routing, and the countless sub-tasks that agent systems generate.

  • 99.9% SLA
  • Official Discounts
  • Pay-as-you-go
  • Fast & Low Latency
Brand:OpenAIPrice: Tiered pricing

GPT-5.6 Luna: Model Introduction & Practical Guide

GPT-5.6 Luna is the "moon" of OpenAI's GPT-5.6 family - the lightweight tier built for speed and low cost rather than maximum reasoning depth. Where Sol tackles security research and Terra handles daily professional work, Luna is the model you deploy at scale: classification, extraction, drafts, routing, and the countless sub-tasks that agent systems generate.

Here's the short version: in an agentic economy, most model calls are small. An agent that decomposes a task might issue ten tool calls, three classification steps, and five extraction passes for every one "hard" reasoning step. Luna exists to make those high-frequency calls cheap and fast, while keeping the same 1.5M-token context window as its siblings so it can still read the long inputs that flow through multi-step pipelines. It is available across ChatGPT, Codex, and the API with effort controls. The trade-offs are exactly what you'd expect from a lightweight tier - reduced depth on complex reasoning - so the skill in using Luna well is routing: send the hard 10% to Sol or Terra, and let Luna carry the volume.

This guide covers model overview, core features, technical specifications, capability comparison, core advantages, recommended use cases, example prompts, and selection recommendations.


Quick Facts

AttributeValue
Model nameGPT-5.6 Luna
DeveloperOpenAI
ReleaseJune 27, 2026 (GPT-5.6 family)
Family positionLightweight tier (Sol flagship · Terra balanced · Luna lightweight)
PositioningSpeed and lowest cost
Context window1.5M tokens
AvailabilityChatGPT (Plus and above selectable), Codex, OpenAI API
Effort controlsAdjustable levels
ModalitiesText, image input
Best forHigh-volume classification, extraction, drafts, agent sub-tasks, routing

Table of Contents

  1. Model Overview
  2. Core Features
  3. Technical Specifications
  4. Capability Comparison
  5. Core Advantages
  6. Recommended Use Cases
  7. Example Prompts
  8. Selection Recommendations
  9. FAQ
  10. Sources & Further Reading

1. Model Overview

OpenAI's tiering for GPT-5.6 is an economic statement about how AI work actually distributes: a small fraction of calls need the smartest model, and a large majority need a fast, cheap one that's good enough. Luna is that second model. It carries the family's 1.5M-token context window - so it can ingest the same long inputs as Sol and Terra - but targets the latency and price profile of high-throughput production use.

The natural habitat for Luna is inside agent systems. When a Work or Codex agent decomposes a complex task, the resulting sub-tasks are overwhelmingly small: "classify this ticket," "extract these fields," "draft this section," "check whether this output satisfies the format." Each of those calls is cheap on Luna and wasteful on a flagship. Similarly, batch pipelines - document processing, content tagging, structured extraction across thousands of files - are Luna territory by design.

Availability follows the family pattern: selectable in ChatGPT (Plus and above), available in Codex, and exposed through the API alongside Sol and Terra, with effort controls for tuning. The pragmatic architecture for most teams is a router: Luna for volume, Terra for the middle, Sol for escalation - all sharing one context size and tooling surface, which keeps the pipeline simple.

2. Core Features

Speed and lowest cost. The cheapest and fastest tier in the GPT-5.6 family - built for volume.

1.5M-token context. Family-parity context window, so long documents flow through Luna-based pipelines without chunking gymnastics.

Effort-level controls. Adjustable reasoning depth to squeeze out additional latency or cost when tasks allow.

Tool calling. Function calling for agent sub-tasks and structured workflows.

Broad availability. ChatGPT, Codex, and API with tier selection.

Family interoperability. Same context size and interfaces as Sol and Terra - simple routing between tiers.

3. Technical Specifications

SpecificationDetail
FamilyGPT-5.6 (Sol / Terra / Luna)
PositioningLightweight - speed and lowest cost
Context1.5M tokens
AvailabilityChatGPT (Plus+), Codex, API
ModalitiesText, image input
Effort controlAdjustable levels
Primary useHigh-volume and latency-sensitive tasks

4. Capability Comparison

DimensionGPT-5.6 LunaGPT-5.6 TerraGPT-5.6 Sol
DepthGood enough at speedGPT-5.5-classFrontier
CostLowestHalf of prior flagshipPremium
LatencyFastestModerateHigher
Context1.5M1.5M1.5M
Sweet spotClassification, extraction, draftsDaily analysis and assistanceHardest technical work

Routing pattern. The recommended architecture: Luna handles routing decisions and sub-tasks, Terra carries mainline generation, Sol escalates the hard 10%. Because all three share the 1.5M-token context and OpenAI's tooling, switching between them is a model-ID change rather than a pipeline rebuild.

5. Core Advantages

  1. Volume economics. The lowest per-call cost in the family makes high-frequency agent loops affordable.
  2. Latency for interactivity. Fast responses keep user-facing features and agent chains snappy.
  3. Family context parity. 1.5M tokens means no chunking penalty for long inputs at the cheap tier.
  4. Clean escalation. Upgrade any specific call to Terra or Sol without changing anything else.
  5. Simple mental model. One family, three price/quality points, shared tooling.
  • Classification and routing: intent detection, ticket triage, content tagging at scale.
  • Structured extraction: fields, entities, and tables from documents and messages.
  • Draft generation: first-pass copy, summaries, and outlines for human polish.
  • Agent sub-tasks: tool-call preparation, format checking, and step verification.
  • Batch document pipelines: processing thousands of files where per-unit cost dominates.
  • Consumer-scale features: chat suggestions, autocomplete, and lightweight assistants.

7. Example Prompts

1. Classification at scale

text
Classify each of the following support messages into: billing, bug,
feature request, or other. Also output a confidence 0-1 and a one-line
reason. Input format: JSONL, one message per line.

2. Structured extraction

text
From each invoice in this batch, extract: vendor, invoice number, date,
line items with amounts, tax, and total. Output strict JSON matching the
schema provided. Flag any invoice where fields are missing.

3. Draft pass

text
Draft a 120-word product description for each of these 50 features,
using the tone guide provided. Keep sentences under 18 words. This is a
first draft for human editing.

4. Agent sub-task

text
Given this tool schema and the user's request, decide which single tool
to call first and produce the exact JSON arguments. If no tool applies,
output {"tool": null} with a reason.

5. Format verification

text
Check whether this model output conforms to the required JSON schema.
Return pass/fail, and if fail, the minimal corrected version.

8. Selection Recommendations

Choose GPT-5.6 Luna if:

  • Your workload is high-volume and latency-sensitive.
  • Tasks are classification, extraction, drafting, or verification rather than deep reasoning.
  • You build agent systems where most calls are sub-tasks.
  • You need long inputs (1.5M context) processed at the lowest cost tier.

Route elsewhere when:

  • The task requires multi-step reasoning, novel problem solving, or domain research - use Terra or Sol.
  • Output accuracy is business-critical and errors are expensive - escalate to Terra.

Sources & Further Reading


Tier details and availability are as published at review time; pricing and access change periodically. Benchmark performance for lightweight tiers varies by task - validate on representative samples before routing critical workloads.