Connect Goose to ApiClo

Before you start

• Create a separate ApiClo API key and check balance and the selected model's current rates.
• Use the client version matching the linked documentation. Keep credentials out of project files.

Steps

1. Connection

   In Configure providers, add a custom OpenAI Compatible provider named ApiClo and enable authentication. For a full request URL use https://apiclo.com/v1/chat/completions.

2. Model and credentials

   If using Goose's built-in OpenAI provider instead, set OPENAI_HOST=https://apiclo.com and OPENAI_BASE_PATH=v1/chat/completions. Do not duplicate the path in both fields.

3. Verification

   Add your selected model IDs, enable streaming when supported, and test a short response. Verify tools and image delivery separately; a custom-provider entry alone does not establish vision support.

Check the result

Send one small request and inspect ApiClo Logs for the exact model, outcome and charged usage. Test tool calls and images separately. Cache settings in the client do not prove a hit: check actual read/write token counts.

Troubleshooting

• A 404 can come from the wrong request path. If the key is ignored, use the provider's credential setup; do not assume a secret pasted into config.yaml is read as an API key.
• For 401, check the active key and credential source; for 404, check the request URL and model ID. Preserve the sanitized error body for support.

Compatibility and billing

ApiClo is an independent gateway. A client integration does not include that client's subscription or guarantee all its features. Compare ordinary input, cache reads, cache writes and output at current model rates; cache hits and savings are workload-dependent.

Sources

• Goose