Access larger context windows on eligible models by appending the :extended suffix.
Not yet available.
Some models offer an extended context window beyond their standard limit. Append :extended to an eligible model slug to unlock that larger window. This is useful for processing long documents, large codebases, or multi-turn conversations that exceed the default context length.
The :extended suffix routes the request to the provider and model configuration that supports the larger context. The model field in the response echoes the full slug with the suffix.
| Variant | Context window | Notes |
|---|---|---|
| Standard (no suffix) | Model's default | Lower per-token cost |
:extended | Larger window (model-specific) | Higher per-token cost; check catalog |
The exact context limits for each model are in the catalog at GET /api/models/{slug}. The :extended context size is listed as context_length_extended when the model supports it.
Extended context is best for:
For most interactive use cases, the standard context window is sufficient and costs less per token in DA.
Extended-context requests are billed at the model's :extended per-token rate, which is higher than the standard rate. The exact DA cost per million input/output tokens is in the model catalog. Because prompts using extended context tend to be longer, estimate your request cost before sending to avoid surprises.
Use the catalog endpoint to compare rates:
The response includes both pricing.standard and pricing.extended in DA per million tokens.
Note. Requesting
:extendedon a model that does not support it returns a404 model_not_founderror. Confirm support in the catalog before using this variant in production.