BUILD
Models & T1 profiles
You don’t pick a raw model name. You pick a T1 profile, a routing strategy that continuously selects the best available model, tools and reasoning depth for your task.
The three profiles
| Profile | Best for | Character |
|---|---|---|
t1-core | Classification, extraction, support, search, high-volume agents | Fast, efficient, grounded |
t1-flow | Connected tools, teams, long-running creative work (default) | Adaptive orchestration |
t1-max | Research, code, strategy, consequential or multimodal work | Maximum reasoning depth |
Selecting a profile
// Fast + cheap
await taskclan.run({ profile: "t1-core", goal: "Classify this ticket" });
// Balanced default
await taskclan.run({ profile: "t1-flow", goal: "Plan and draft the release notes" });
// Deep reasoning
await taskclan.run({ profile: "t1-max", goal: "Review this architecture for risks" });Why profiles, not model names? The frontier moves constantly. Profiles let us route to the strongest model available for your task, and improve it over time, without you changing a line of code.
Model independence
Behind T1, requests may be served by leading open and proprietary models. Providers process your request under terms that restrict training on your data. We never train foundation models on your content without an explicit opt-in, see the AI Policy.
Controlling cost & latency
- Default to
t1-corefor anything high-volume or latency-sensitive. - Reserve
t1-maxfor tasks where quality clearly justifies the cost. - Set
maxTokensand timeouts to bound spend on open-ended goals.