Model Provider Quickstart
Fased uses one provider registry for onboarding, CLI, Agent setup, Chat, tasks, and channel-routed Agents. The normal browser surface is Agent > Models for the selected Agent.Quick Start Path
- Open Agents, select an Agent, and use Agent > Models to add a credential, sign in, paste a token, or configure a local/manual endpoint.
- Choose that Agent’s primary/fallback/task model roles on the same page.
- Use Chat to test the Agent. Chat can override the model for the current session when the route is usable.
- Use Agent > Channels to route external apps to that Agent.
- Use Usage when you need local token totals grouped by provider, model, Agent, session, task, or channel.
Pick The Provider Shape
| Shape | Start with |
|---|---|
| Hosted API or sign-in | OpenAI, Anthropic, Chutes, or another provider page. |
| Router or aggregator | OpenRouter, Vercel AI, LiteLLM, or Cloudflare AI Gateway. |
| Local model | Ollama, LM Studio, or vLLM-compatible. |
| Custom endpoint | Custom Provider. |
Catalog Maintenance
Usefased providers refresh to compare the checked-in provider registry with
live or reviewed source catalogs. Use fased providers refresh --write-review
before applying model or capability changes.
Use fased providers models add/remove for local or custom model entries on the
current machine.
See Model providers for the exact refresh and
manual-model commands.
Provider docs intentionally list only first-class Agent > Models providers.
Use Ollama for native Ollama, LM Studio
for localhost:1234, vLLM-compatible for vLLM, SGLang, TGI,
LocalAI, FastChat, and similar OpenAI-compatible local servers, and
Custom Provider when the shortcut does not fit.
Provider setup shows account/endpoint health: reachable, auth ok, models
discovered, and private network approved. Token and cost accounting remains on
Usage, where it is based on Fased’s local usage history rather than provider
quota screens.