Use DaoXE in Cline

Cline speaks to any OpenAI-compatible endpoint, so switching it to DaoXE is a base-URL-and-key change — no proxy, no fork. The payoff: one key for the cheapest APIs guide across vendors, and an agent that can plan on a frontier model and edit on a cheaper one.

Why route Cline through DaoXE#

• One key, many models. Swap the agent's model without juggling per-vendor accounts, cards or bills.
• Route by cost. A small model for routine edits, a frontier model for planning — all on one balance.
• Native tool calling. Cline's agentic edits and command runs behave as expected when the model supports tools.

Set it up in Cline#

1. Open the provider settings. In the Cline panel, click the settings gear and set API Provider to OpenAI Compatible.
2. Set the Base URL. Enter https://daoxe.com/v1 — end it at /v1, not /chat/completions (Cline appends the path itself).
3. Paste your key and Model ID. Add your DaoXE key, then a Model ID copied verbatim from GET /v1/models. Guessed names fail.
4. Click Verify. Cline sends one live request; once it passes, run a small task to confirm edits and tool use work.

Verify you actually get the model#

Prove the endpoint works before blaming the client — if this fails, no setting will fix it:

export DAOXE_API_KEY="your_api_key"

# List the exact model IDs your account can call
curl --fail-with-body --show-error --silent \
  https://daoxe.com/v1/models \
  -H "Authorization: Bearer ${DAOXE_API_KEY}"

A cheaper endpoint is only a saving if it serves the real model. Prove connectivity first, then diff outputs against the official API at temperature 0:

curl --fail-with-body --show-error --silent \
  https://daoxe.com/v1/chat/completions \
  -H "Authorization: Bearer ${DAOXE_API_KEY}" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "YOUR_EXACT_MODEL_ID",
    "max_tokens": 64,
    "messages": [{"role": "user", "content": "Say hello in one sentence."}]
  }'

Frequently asked questions#