Skip to main content

Neovate Code

Before you start

You need a Divyam account and an API key. If you don't have them yet, follow Getting Started first.

Replace the shortened divyam-sw-v1-... shown in examples with your complete API key.

The examples use divyam-as/gpt-6-sol. For another model, select its current ID in your harness or copy it from Models and pricing, and check its context limit and supported features.

1. Install Neovate Code​

Install Neovate Code using the official instructions.

2. Add the Divyam provider​

divyam-as/

Model ID: divyam-as/gpt-6-sol. Context window: 1,050,000 tokens. Models and pricing

Merge this into ~/.neovate/config.json. Keep your other providers and replace divyam-sw-v1-... with your Divyam key:

{
"model": "divyam/divyam-as/gpt-6-sol",
"provider": {
"divyam": {
"options": {
"baseURL": "https://api.preview.divyam.ai/v1",
"apiKey": "divyam-sw-v1-..."
},
"models": {
"divyam-as/gpt-6-sol": {}
}
}
}
}

This provider uses Neovate’s default Chat Completions format. You can use this provider without a Neovate account.

3. Start an interactive session​

From your project folder, run:

neovate

Review proposed changes and tool approvals in the terminal.

In Neovate Code's composer
Hello, what are your capabilities?
Paste this message, then send it.
Usage and charges

Neovate’s local token totals can show zero. Use the Divyam console for usage and charges.

Feature limits

To shorten a conversation, run /compact, then continue your conversation. Neovate's file-read tool sends image content as text on this provider route, so use it for text files. Browsing, MCP and delegation are outside this guide.

Check your requests​

Open the Divyam console and select Logs. Your requests appear there within a few seconds, newest first, with their status, token counts and latency. Usage and Credits & Billing catch up within a few minutes.

Local cost estimates

Some clients display zero when model prices are missing. Check Credits & Billing for Divyam charges. Local dollar limits depend on the client's price and usage data.

For filters, cached-token counts and the requested-versus-routed view, see Logs and usage.