Connect Crush 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

   Open ~/.config/crush/crushrc on Unix or %USERPROFILE%\.config\crush\crushrc on Windows. Add the provider commands there, not as ordinary commands in PowerShell.

2. Model and credentials

   Set APICLO_API_KEY before starting Crush. Register a model with model add using its exact ApiClo ID and select it with model large.

3. Verification

   Set --supports-images true only when the selected model accepts images. Confirm a small text task first, then a tool call and a picture with a text question.

Examples

export APICLO_API_KEY="YOUR_APICLO_KEY"

$env:APICLO_API_KEY="YOUR_APICLO_KEY"

provider add apiclo --name "ApiClo" --type openai-compat --base-url "https://apiclo.com/v1" --api-key "$APICLO_API_KEY" --discover-models false
model add apiclo/claude-sonnet-5 --name "Claude Sonnet 5" --supports-images true
model large apiclo/claude-sonnet-5

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

• Do not mix legacy JSON and current crushrc syntax. If the provider works but attachments fail, check the selected model's supports-images setting and actual model support.
• 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

• Crush