Skip to main content
Velqa

Tool integrations — connect your coding agents to Velqa

Velqa exposes an OpenAI-compatible API, so any OpenAI-compatible client (opencode, Cline, Roo Code, Kilo Code, Continue…) works with no plugin: you just change the base_url and the key.

Checkout is Stripe, in USD, by international card. Moroccan-issued cards are not accepted here: customers in Morocco are served by velqa.ma, where dirham checkout by Moroccan card opens soon.

The idea: one base_url + one key

Most agentic tools already know how to talk to an OpenAI-compatible API. You only need three values:

SettingValue
Base URLhttps://api.velqa.dev/v1
API keysk-... (created in the dashboard)
Model IDan identifier from the velqa.dev/models list, e.g. minimax-m3

Note: some guides below use https://api.velqa.dev/v1 as the base URL — both point to the same OpenAI-compatible gateway. Use exactly the value shown in your tool's guide.

For Claude Code, Velqa additionally exposes an Anthropic-compatible endpoint (/v1/messages) at https://api.velqa.dev: Claude Code then works natively, with no local proxy.

Per-tool guides

ToolTypeGuide
opencodeCLI, OpenAI-compatibleopencode
Claude CodeCLI, Anthropic-compatibleClaude Code
ClineVS Code extension, OpenAI-compatibleCline
Roo CodeVS Code extension, OpenAI-compatibleRoo Code
Kilo CodeVS Code extension, OpenAI-compatibleKilo Code
ContinueVS Code / JetBrains extension, OpenAI-compatibleContinue

Each guide gives the exact configuration (file paths, UI fields), the per-model context window values and an end-to-end test.

One-click config snippets

The Integrations page in your dashboard generates a ready-to-paste config snippet for each tool, and lets you create a named key per tool (one key per machine or per project, revocable independently). It's the fastest way to get started without copying values by hand.

Going further