CLI Tools

Factory Droid

Add a generic Chat Completions model in Factory user settings.

ConfigurableOpenAI Chat CompletionsDocs checked 2026-09-18

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

On this page

Before you begin

Install Droid CLI and choose a tool-capable model. Follow Factory’s current account and product-access requirements.

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.

Manage API keys Browse models

Setup

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

01Install Droid
Follow the official quickstart to install Droid and complete its first launch.
Open official documentation

02Merge a custom model

Preserve existing settings and add the model to customModels. Keep maxOutputTokens within the model’s output limit.

~/.factory/settings.json

{
  "customModels": [{
    "model": "YOUR_MODEL_ID",
    "displayName": "A2Agent",
    "baseUrl": "https://a2agent.me/v1",
    "apiKey": "${A2AGENT_API_KEY}",
    "provider": "generic-chat-completion-api",
    "maxOutputTokens": 4096
  }]
}

03Launch and select the model
After launching, select A2Agent with /model.
Shell
```
export A2AGENT_API_KEY='YOUR_A2AGENT_API_KEY'
droid
```

Capabilities and limits

generic-chat-completion-api and the openai provider use different protocol behavior; do not swap them casually.
Check BYOK model billing separately from Factory product access.

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 the model is missing, check customModels casing, JSON syntax and the settings.json path, then restart.

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

Switch back with /model, remove the customModels entry, and close the terminal holding the key variable.

Sources and check date

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

Docs checked 2026-09-18