CLI Tools

Goose

Use the OpenAI provider with separate host and request-path 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 Goose CLI from the official guide and choose a tool-capable model. Back up existing OpenAI settings 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.

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 the CLI
Install the CLI using the official guide. The configuration wizard does not accept arbitrary model names; the next step sets the model through the environment.
Open official documentation

02Set the endpoint and model, then launch

OPENAI_HOST takes only the root URL; OPENAI_BASE_PATH supplies the path. Replace the model ID and key, then launch in the same terminal.

Shell

export GOOSE_PROVIDER='openai'
export GOOSE_MODEL='YOUR_MODEL_ID'
export OPENAI_HOST='https://a2agent.me'
export OPENAI_BASE_PATH='v1/chat/completions'
export OPENAI_API_KEY='YOUR_A2AGENT_API_KEY'
goose session

Capabilities and limits

Do not add /v1 to OPENAI_HOST.
Keys can come from the environment or system credential storage. Do not assume a same-named config.yaml entry takes effect.

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

A duplicated host/path can cause a 404. If the model did not change, check GOOSE_PROVIDER and GOOSE_MODEL in this terminal, then start a new session.

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

Close the terminal to discard these environment variables. If saved in a shell profile, remove the added entries and restore previous values.

Sources and check date

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

Docs checked 2026-09-18