condensate docs
Build and connect / Condensate

Accounts and model routing

Separate credentials, provider models, and the runtime's routing policy.

A model name, an engine, and an account identify different parts of a request. The model specifies what generates the answer. The engine runs the session. The account supplies provider access.

What a model request needs
AccountCredentials for provider access
ModelThe selected provider model
EngineThe compatible session loop
These are separate configuration choices that must agree. The arrows show a configuration checklist, not a credential transmission path.

Configure an account

Use the account setup surface in the running application or the runtime's supported login flow. Store provider credentials in the configured account system, outside the checkout. Do not paste token values into workspace JSON, documentation, or task briefs.

The credential broker and runtime account routes handle account access and refresh. Login modes vary by provider; the existence of a provider transport does not guarantee your subscription permits every API feature or model.

Check a real turn

Reading an account record or starting a server confirms configuration, not model access. Verify the selected account with a small real turn and inspect its result. That check consumes provider usage.

Route a model request

The engine's ModelRouter resolves configured profiles into engine, model, effort, thinking, and failover settings. The routing document is schema-validated. A model and engine mismatch is rejected before the session is built.

Failover is conditional on the classified failure and configured policy. Do not assume that every error will switch models or that switching the default account changes an already-materialized session.

Diagnose the correct layer

SymptomCheck
Account listed, but provider refusesActual account credentials and provider response
Model rejected before a turn startsEngine/model compatibility and workspace model policy
Another account becomes default, old task unchangedThe existing session's binding
Task changes models after failureFailure classification and configured fallback chain

Inspect the available models

The runtime exposes its completion model catalog:

curl -fsS http://127.0.0.1:4741/v1/models

The returned catalog describes this runtime's completion surface. Access still depends on the configured account. Use the application's model picker and inspect an actual turn when configuring durable agent tasks.

Condensate developer documentation · Source ba6d28952e