Integration guides · 2026-09-22
Dots3-Note Preview shuts down on 30 September: a migration checklist
Dots Studio's free 512K-context model shuts down on 30 September 2026, with no named successor. This covers the concrete steps to take before the cutoff.
Not a guess — a date already recorded in the catalog
Dots3-Note Preview's model page states clearly that the row shuts down on 30 September 2026. The model keeps working normally until then; after that, requests for this identifier are not silently rerouted to another model, they return a model_retired error directly. Because there's no silent reroute, not having a ready alternative in hand at shutdown can stop your production flow.
The catalog currently has no named successor: no other row offers free access, a 512K context window, and image input at the same time. That means the migration is not automatic — it's your own choice to make.
Concrete steps to take before the shutdown
First, find every place `dots-studio/dots-3-note-preview` appears in your production code; this can take minutes or hours depending on whether the model identifier lives in a configuration value or is hard-coded. Then pick the catalog row closest to your actual need (a smaller context window may be enough if you don't need 512K, and a text-only model is also an option if you don't need image input) and test it with a real request.
The model's reasoning is on by default, and whether it can be turned off has not been measured; separately check how that behavior is controlled (if at all) on the model you choose, since it may need a different parameter than your old code.
- Find every place dots-studio/dots-3-note-preview appears in production code.
- Pick the active catalog row closest to your need and test it with a real request.
- Assume the new model's thinking/reasoning control may work differently from the old code.
The free quota limit continues until shutdown
The model keeps being offered free with a daily usage quota until it shuts down; once the quota is reached, requests are limited until the next day. Leaving migration until the last minute means running into the quota limit and the shutdown deadline's pressure at the same time; testing early reduces that risk.
Frequently asked questions
What happens if I send a request to this model after 30 September?
The request is not automatically rerouted to another model; you get a model_retired error directly. You need to update your production code before that date.
Is there a direct successor model?
No, no other row in the catalog currently offers free access, a 512K context window, and image input at the same time. You need to choose the new model yourself based on your own need (context length, image input requirement, budget).