Models
Choose the execution profile that matches the work. WEDNESDAY owns the routing contract while retaining freedom to improve the underlying provider route as long as the published profile behavior remains compatible.
Choose an execution profile
Default conversational profile for responsive, general-purpose work with balanced reasoning and latency.
Higher-reasoning profile for complex analysis and tasks where depth matters more than minimum latency.
Code-oriented execution route used when the runtime classifies the work as software-development heavy.
Routing is observable
The streaming protocol can represent resolved routing information for a turn, including a model identifier, model role, requested and resolved intelligence level, latency profile, reasoning profile, and bounded completion behavior. Those fields make execution observable; they do not automatically turn every internal route target into a permanently supported developer model.
Public model contract
A named developer model becomes part of the public catalog only when WEDNESDAY publishes all of the following:
- a stable WEDNESDAY model identifier;
- supported input and output modalities;
- tool compatibility;
- public limits developers may rely on;
- lifecycle state;
- migration guidance when behavior is replaced or retired.
Model selection
Use the product-level intelligence and latency controls documented by the interface that exposes them. For routine work, start with Balanced. Use Deep Reasoning when task difficulty justifies additional reasoning. Code-oriented work can resolve to the Coding profile through runtime routing.
Lifecycle
Public model contracts follow an explicit lifecycle. Deprecation is announced through Deprecations and the Changelog before a supported identifier is removed or materially changed.