Provider billing is separate
Your provider charges model tokens directly. DevCoreAI plans cover platform access, automation, team features, and governance.
DevCoreAI currently works as BYOK: you connect your own provider keys, your provider bills model usage directly, and DevCoreAI gives you the agent workspace, approvals, settings, platform limits, and dashboard experience.
Your provider charges model tokens directly. DevCoreAI plans cover platform access, automation, team features, and governance.
Store provider keys only in DevCoreAI settings. Do not paste secrets into prompts, docs, screenshots, or issue comments.
Match model strength to risk. Use stronger models for architecture and security, faster models for small edits.
Fast coding, general reasoning, and broad tool support.
Large refactors, architecture planning, careful code review, and long context workflows.
Long-context analysis, broad repository reading, and cost-sensitive workflows.
Trying many providers from one API key and quickly switching between models.
Private experimentation, offline-friendly workflows, and cost control for simpler tasks.
| Setting | How it works |
|---|---|
| Provider | The service DevCoreAI sends model requests to. Change this when switching from one model company or router to another. |
| API key | Your provider credential. Keep it private, rotate it if exposed, and never paste it into normal chat messages. |
| Base URL | Used for local models, compatible gateways, self-hosted proxies, or enterprise model routers. |
| Model | Controls output quality, context size, speed, and provider cost. Use stronger models for high-risk work. |
| Reasoning effort | Controls model depth when supported. Higher effort is useful for architecture, security, debugging, and multi-file refactors. |
| Plan/Act model split | Lets you use one model for planning and another for implementation. This can reduce cost while keeping analysis quality high. |
Use a fast, cost-efficient model in Act mode.
Use a stronger reasoning model, start in Plan mode, and keep approvals manual.
Use a long-context model and ask DevCoreAI to analyze before editing.
Use OpenRouter or a compatible router, then pin the best model per workspace.
Use Ollama or LM Studio, but verify model quality before production edits.
In team or enterprise environments, admins may use DevCoreAI remote policy to limit providers, hide unsupported models, require manual approvals, or disable risky integrations. User and workspace settings still appear inside the IDE, but some values may be locked by organization policy.
Create a new key, paste it into API Configuration, save, and confirm the provider account has billing or credits enabled.
Check the exact provider model ID, account access, region availability, and whether an admin policy hides that model.
Wait for quota reset, upgrade provider limits, choose a lighter model, or reduce parallel agent activity.
Confirm the local server is running, base URL is correct, model is downloaded, and firewall rules allow local access.
Use Plan/Act split, lower reasoning effort for simple work, avoid huge context uploads, and review provider billing logs.
Ask your workspace or organization admin to review DevCoreAI remote policy. User settings may be read-only when policy is enforced.
Start in Plan mode for the first real task. Ask DevCoreAI to inspect the codebase and propose a plan before approving edits.
Continue to Plan and Act