Pointing VS Code Extensions Like Continue and Cline at an Aggregator Endpoint

Why Point Extensions at an Aggregator

AI coding extensions like Continue and Cline normally require you to configure each model provider separately. That means managing multiple API keys, billing accounts, and possibly KYC processes. An aggregator endpoint simplifies this: you get one API key that works across many models, and you can top up with USDC on Base without KYC.

How Aggregators Work

An aggregator sits between your extension and the model providers. When you send a request, it routes to the chosen model and returns the response. Key points:

• You pay the official price multiplied by 1.3.
• Key contributors are credited the official price multiplied by 1.1 (or 1.2 for premium) in USDC.
• No KYC is required for top-ups.

This model keeps things simple and transparent.

General Configuration Steps

Most extensions that support custom endpoints follow a similar pattern:

1. Get an API key from the aggregator.
2. Find the base URL for the aggregator's API (often compatible with OpenAI's API format).
3. Open the extension's settings in VS Code.
4. Add a new model provider or edit an existing one.
5. Enter the base URL and API key.
6. Select a model from the aggregator's supported list.
7. Save and test with a simple prompt.

Configuring Continue

Continue uses a config.json file for model configuration. To add an aggregator:

• Open the Continue configuration file (usually via the Continue sidebar).
• Add a new entry under models.
• Set provider to openai (if the aggregator is OpenAI-compatible) or a custom provider if supported.
• Set apiBase to the aggregator's base URL.
• Set apiKey to your aggregator API key.
• Specify the model name as listed by the aggregator.

Example snippet (conceptual):

{
  "models": [
    {
      "title": "Aggregator Model",
      "provider": "openai",
      "model": "model-name",
      "apiBase": "https://api.aggregator.com/v1",
      "apiKey": "your-api-key"
    }
  ]
}

Configuring Cline

Cline (formerly Claude Dev) allows custom API providers in its settings:

• Open VS Code settings and search for Cline.
• Choose "API Provider" and select "OpenAI Compatible" or similar.
• Enter the base URL and API key.
• Pick a model from the aggregator's list.

Cline may also support other provider types; check its documentation for specifics.

Tips and Considerations

• Model names must match exactly as listed by the aggregator.
• Rate limits are set by the aggregator; check its docs for details.
• Billing is based on usage at the aggregator's rates.
• Testing with a simple "Hello" prompt helps verify the setup.
• Security: keep your API key private; do not commit it to version control.

Troubleshooting Common Issues

If the extension fails to connect:

• Verify the base URL includes the correct path (e.g., /v1).
• Ensure the API key is valid and has sufficient balance.
• Check that the model name is correct.
• Look at the extension's output logs for error messages.

Conclusion

Pointing VS Code extensions like Continue and Cline at an aggregator endpoint streamlines your AI coding workflow. You gain access to multiple models with one key, pay with USDC on Base, and avoid KYC. Follow the steps above to get started.