All integrations

AI Editors

Qoder

Add a custom OpenAI-compatible provider and verify model capabilities.

ConfigurableOpenAI Chat CompletionsDocs checked

The vendor documents custom endpoints. Check model capabilities and verify the connection.

On this page

Before you begin

Install current Qoder with custom-model support. Account and organization requirements still apply; the CLI has a different BYOK entry.

Have an A2Agent API key ready and copy an accessible model ID from the catalog. Replace every placeholder, back up existing settings and keep keys out of repositories.

Setup

File contents are usually shared; switching OS changes commands and paths. For WSL on Windows, select macOS / Linux.

  1. 01Add a provider

    Open Settings → Models → + Add. Select Custom OpenAI Compatible and the Chat Completions API type.

    Open official documentation
  2. 02Enter and verify

    Enter the URL, key and at least one model ID. Check context, vision and reasoning capabilities, then verify and add.

    text
    Base URL: https://a2agent.me/v1
    API Key: YOUR_A2AGENT_API_KEY
    Model ID: YOUR_MODEL_ID

Capabilities and limits

  • Features such as Repo Wiki have their own model and credit arrangements. This setting does not switch every feature.
  • If choosing Responses instead, confirm that the model and key group support it.

Verify the connection

Replace every placeholder and run locally. Expect JSON containing OK. Then start a new client conversation, test one read-only tool call separately, and confirm the requests in A2Agent usage records. This test incurs a small amount of model usage.

Shell
curl --fail-with-body --silent --show-error --max-time 60 'https://a2agent.me/v1/chat/completions' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_A2AGENT_API_KEY' \
  -d '{"model":"YOUR_MODEL_ID","max_tokens":128,"messages":[{"role":"user","content":"Reply with OK."}]}'

Troubleshooting

If verification fails, check the API type first. For tool or image failures, check whether capability declarations exceed model support.

401 / 403: authentication or access denied

Use a key issued by A2Agent, without extra spaces, and check that it is active and unexpired. Confirm the group permits the model and protocol. A vendor subscription credential cannot replace an A2Agent key.

404 / model not found: endpoint or model mismatch

Check the root URL, /v1 prefix and full request path against this guide; avoid duplicated paths. Model IDs are case-sensitive and must be accessible to the current key.

429: quota or rate limit

Check your balance, key limits, concurrent usage and service status. Wait before retrying and reduce simultaneous agents; repeated retries do not remove a quota limit.

Chat works, but tools fail or streaming stops

Test a short text request, then a single read-file tool call. Check tool support, output budget, proxy timeouts and client version. Inspect the diff before resuming a long task to avoid repeating actions.

Restore previous settings

Select the previous model and remove the added provider or model and key in settings.

Sources and check date

Status is based on official configuration docs, not end-to-end client testing with A2Agent.

Docs checked 2026-09-18