Skip to content

Your models.
One connection layer.

LibraOS Gateway provides model API access and routing. AgentD manages the development tasks and workers using those models.

Keep the roles clear.

Choosing a model and delegating a task are different decisions.

AgentD
Owns task coordination, handoffs, worker budgets, checks and results.
LibraOS Gateway
Connects compatible inference APIs. Provider protocols and models must be configured and validated for each client.
Your coding clients
Claude Code and Codex use their configured accounts or compatible endpoints. AgentD does not include model access.
Dashboard Chat
Needs a compatible gateway configuration of its own. It does not reuse a coding client’s sign-in.

Choose your connection.

Your provider

Bring the account or credentials supported by your coding client. Your provider bills usage.

LibraOS model API

Configure compatible clients through Console. Access and usage billing are separate from AgentD Local.

Local endpoints

Use compatible self-operated endpoints where supported. Verify protocol compatibility and behavior in your own workflow.

Model mirrors and quantizations are not LibraOS fine-tunes unless a model card says so.

Understand the costs