Trust and security · 2026-09-22
Sincap has been retired: where to move your free-trial flow
Covers that the llmtr/sincap experimental model has been shut down on the provider side, stays in the catalog with retired status, and how to move a trial/prototype flow depending on this identifier.
What the model page says
llmtr/sincap isn't LLMTR's own model and isn't hosted in Turkey; the catalog description states this plainly and describes the model as a free trial model offered for teams wanting to explore alternative writing styles and test lightweight assistant flows — not for critical production work, for exploration and prototype scenarios. The model page now carries the 'Sağlayıcıda kapalı' (closed at provider) status label and is marked retired (isRetired) in the catalog.
Per this repo's convention, a retired model isn't fully removed from the catalog; the page and URL stay, but requests are no longer answered on the provider side. An integration still sending requests to this identifier will run into an error response.
How to move a flow depending on this identifier
Sincap carried only text input/output and zero cost (free); it didn't offer an extra capability like function calling or image input. That means the migration target needs to match at least the same base capability set (text input/output), but there's no extra-capability expectation to satisfy.
Filtering for rows carrying a 'Free' status label in the current model catalog can find an alternative suited to a similar exploration/prototype purpose; every free model carries its own quota and data-policy terms, so separately read the newly chosen model's data-policy note (whether prompts are logged by the provider, for example).
- Sincap offered only text input/output; don't expect an extra capability.
- Filter for 'Free' status rows in the current catalog to look for an alternative.
- Separately read the new model's data-policy note; each free tier's terms differ.
It shouldn't have been in a critical production flow anyway
The model page always stated this was for exploration and prototyping, not critical production work; this retirement is a smooth transition for a flow that followed that advice, and an architectural mistake that now needs fixing for one that didn't.
Frequently asked questions
What happens if I keep sending requests to Sincap?
Since the model is closed on the provider side, requests are no longer answered; you need to update your code to a current model identifier.
Does Sincap have an official successor?
The model page doesn't state a specific successor identifier; you need to review the free-status rows in the current model catalog and pick one that fits your need.