All integrations

AI Editors

TRAE

The China edition can add a custom model with a full Chat Completions URL.

LimitedOpenAI Chat CompletionsDocs checked

Configuration is available with version, account, region or feature restrictions. Read the conditions below first.

On this page

Before you begin

This guide checks the China edition’s model documentation. Confirm the equivalent entry in international, managed or older editions first.

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. 01Open custom models

    After installation and sign-in, open Settings → Models → Add model → Custom model. Select Chat Completions.

    Open official documentation
  2. 02Enter the full URL

    Enable full-URL input and enter these values. Set tool and image capabilities to match the model, save, then select it in chat.

    text
    API: Chat Completions
    URL: https://a2agent.me/v1/chat/completions
    API Key: YOUR_A2AGENT_API_KEY
    Model ID: YOUR_MODEL_ID

Capabilities and limits

  • Working chat does not establish that SOLO or other specialized features use the custom model.
  • The full-URL switch changes path handling. Do not combine automatic path appending with a full request path.

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

For a 404, check the full-URL switch. If the entry is missing, check the regional edition and enterprise policy.

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 a built-in model and remove the A2Agent custom model and key from model 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