Bring the models you already pay for.
Knotic credits, your API keys, local endpoints, or Claude Code and Codex subscriptions. Choose the provider per activity and the coding model per Blueprint step.
Working with Models & Providers
Choose a connection
Enter a license key in Settings → License, configure an API in Providers, or connect a vendor CLI in AI Subscriptions.
Check the provider
API models come from the configured endpoint. For a subscription, sign in with the vendor in the integrated terminal.
Pick the activity’s model
Use the selector above the composer, or configure defaults in Settings → Agents.
Choose per step
Architect has a planning model plus coding choices for the whole Blueprint or individual steps.
Models & Providers: the details
Open the details that matter to your workflow.
Knotic models
Artiforge hosts models by role: base, architect, brainstorming, context and utility. Your license key authenticates requests and usage consumes Knotic credits.
Your API keys
Enable an OpenAI-compatible API in Settings → Providers. Keys stay in your OS credential store and are never sent to Artiforge.
Local endpoints
Override a provider’s endpoint to use a local OpenAI-compatible server or a proxy.
Claude Code and Codex
Connect the locally installed CLIs in Settings → AI Subscriptions. Vendor login stays with the vendor. Knotic keeps the conversation, tools, memory, queue and Monitoring.
Free and paid access
Ordinary Sessions and Duckie Chat work with your configured providers without a paid plan. Architect, Brainstorming, Context Lens and Blueprint-bound Sessions use Knotic models with a free key; any active paid plan enables other providers there.
Know the boundaries
- Vendor subscription limits still apply. Knotic does not switch providers automatically.
- Subscription costs are API-equivalent estimates.
- Claude Code and Codex subscriptions are available in the desktop app, not Knotic CLI.